I love the idea of self-hosting, especially since I keep a number of very tiny websites/projects going at any given time, so resources would not really be too much of an issue for me. What stops me is security. I simply do not know enough about securing a self-hosted site on real hardware in my home and despite actively continuing to learn, it seems like the more I learn about it, the more questions I have. My identi…
Self-Hosting like it's 2025
121–130 of 240 posts
Re: Self-Hosting like it's 2025
#122It sure is self hosted! https://localhost:1313/posts/self-hosting-like-its-2025/
Re: Self-Hosting like it's 2025
#123Re: Self-Hosting like it's 2025
#124This site redirects to localhost:1313. Is this some sort of April fool's joke that I'm not getting? $ curl https://kiranet.org/self-hosting-like-its-2025/ //localhost:1313/posts/self-hosting-like-its-2025/
Re: Self-Hosting like it's 2025
#125I can self host many applications, but their security must be outsourced to a company. I don’t have time to keep on top of vulnerabilities. Cloudflare Tunnels is a step in the right direction, but it’s not end to end encrypted. The question is then, how to secure self hosted apps with minimal configuration, in a way that is almost bulletproof?
It's easy to manage and reason about.
Re: Self-Hosting like it's 2025
#126Lol that's hilarious, the url resolves to https://localhost:1313/posts/self-hosting-like-its-2025/ , how ironic!!
Re: Self-Hosting like it's 2025
#127Re: Self-Hosting like it's 2025
#128I love the idea of self-hosting, especially since I keep a number of very tiny websites/projects going at any given time, so resources would not really be too much of an issue for me. What stops me is security. I simply do not know enough about securing a self-hosted site on real hardware in my home and despite actively continuing to learn, it seems like the more I learn about it, the more questions I have. My identi…
Re: Self-Hosting like it's 2025
#129Re: Self-Hosting like it's 2025
#130If you self host, do not use containers and all those things. Just use a static site generator like zola or hugo and rsync to a small VPS running caddy or nginx. If you need dynamic thing, there are many frameworks you can just rsync too with little dependencies. Or use PHP, it's not that bad. Just restrict all locations except public ones to your ip in nginx config if you use something like wordpress and you should…
What I'm reading is not to use containers for a web server, which makes sense because web servers have had vhosts since forever and you can host any number of sites on there independently already But what about other services, like if you want a database server as well, a mail server, etc.? I started using containers when I last upgraded hardware and while it's not as beneficial as I had hoped, it's still an improvem…