41–50 of 74 posts
Why isn't caddy in a container?
It's a single binary file, so there's not a whole lot to be gained unless you're already doing containers in general. When the entire system is this few moving parts, I'm not sure that it's worth the trouble of containerizing it.
This seems both more work and more expensive than GitHub Pages. Hardly the cheap or lazy option. And if the author is reading - your Author link is broken.
Github pages still has no ipv6 support though. Either neocities, netlify or random web hosting company are better options than this imho. Granted one can also fix this problem by sticking a caching CDN with ipv6-support in front.
But this blog post doesn't set up IP version 6 either.
Netlify has a free plan and you don't have to tinker with containers.
If the domain name is owned by somebody else, then they own and control the site, not you.
Anything that starts with "Install Docker" will not be cheap or easy
The key part about having your own personal blog site is owning your own domain. As long as you own the domain, you can change your mind. As long as you own your domain name, you can self-host today, host elsewhere, or whatever you want. If the domain name is owned by somebody else, then they own and control the site, not you.
But if you put up a tor onion service you actually own your domain name. I'm not saying only host on tor, but why not a .onion too?
Probably, I'll just write about my pain about how did I deal with docker, exposing the port, nginx reverse, some vps provider and DNS stuff.
We host our blog using solely off-the-shelf tools, and I love the stack that we use. I highly recommend it if you're looking for a stack with 100% control and are ok with some light technical wrangling (eg using Git): - Jekyll for static site generation https://jekyllrb.com/ - We use the Hydeout Jekyll theme, you can see how it looks on our blog: http://staysaasy.com/ . What you see is out-of-the-box plus ~30 lines o…
Folks also seem to forget that an s3 bucket can host your static website, will cost mostly pennies and pretty much never go down. https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosti...
Or make your blog static and use Netlify.
Doesn't seem to be much point in competing against $0, though the technical side is interesting.
The key part about having your own personal blog site is owning your own domain. As long as you own the domain, you can change your mind. As long as you own your domain name, you can self-host today, host elsewhere, or whatever you want. If the domain name is owned by somebody else, then they own and control the site, not you.
This brings up the related issue of the normal domain name system and it's governence. No one really owns their domains. They lease them at the whim of some corporate or government entity. But if you put up a tor onion service you actually own your domain name. I'm not saying only host on tor, but why not a .onion too?
I mean ownership in the usual sense. There are laws and people who are supposed to enforce those laws so that once you purchase something and obey certain rules, you get to keep it. Perhaps more importantly, if a typical energy says they just want to take it from you, there are courts you can appeal to.
If you post on Facebook, and Facebook takes it down, you have absolutely no right of appeal. If I post material on my personal site on a domain I own, it is harder to take down, and much easier to bring it back. I'm assuming here that the content is not illegal, that's a different issue.