Is there a good alternative to github pages? I need just a static website up.

  • I have a domain.
  • I have my site (local machine)
  • And that’s all I have.
  • I have a machine that could be running 24/7 too.
  • neidu3@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    28
    ·
    edit-2
    2 days ago

    Ok, so I must’ve misunderstood the question, because to me it seems OP already has all the necessary ingredients to bake this dish. And yet, the vast majority of comments recommend various 3rd party services which is the complete opposite of selhosting.
    Fire up nginx/apache2, and all good, no? What am I missing?

    • iveseenthat@reddthat.comOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      16 hours ago

      Hi, thanks for the comment. I have the page. But I don’t know how to make the page accessible from the web.

      I have a router at home that my ISP provided (I cannot even login to it) which provides WiFi and have a couple of Ethernet ports.

      I don’t know if it is possible to make my page available to the world from behind this soho

      • slate@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours ago

        A reverse proxy from somewhere like Cloudflare would allow you to host without any router config. Plus, it’d give a little more protection against bots, but it’s not going to block 100% of them.

      • Zos_Kia@lemmynsfw.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 hours ago

        I honestly wouldn’t recommend it if you don’t have a minimum of security knowledge. The moment your home server pops up with a domain name it will get scanned by shady actors and possibly exploited.

      • neidu3@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        7 hours ago

        Are you able to ask your ISP customer service to set up port forwarding for you?

        At minimal you want HTTP (Port 80) but you probably want HTTPS (443) as well. If you’re hosting DNS as well you will need port 53 too.

        Have those ports routed to the “inside” IP of the machine you want to use, and the rest of it is basically just setting up the webserver (and possibly DNS) to serve your domain.

        NB: While on the phone with your ISP, ask them what the DHCP lease time is. Ideally you want a static IP for your setup.

    • LifeInMultipleChoice@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 day ago

      I was confused when I read it as well, at least I know now that I wasn’t alone. I think the next step is just opening a text editor and starting with <html></html> Forward a couple ports, maybe use caddy to route the port internally but it isn’t needed. Although if you use NOIP with Caddy getting the https cert setup seems to be pretty easy.