Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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?
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
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.
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.
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 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.
I think the missing piece is the website itself? The static HTML page generator?
Something like Hugo