Anything that starts with "Install Docker" will not be cheap or easy
Yup
Self-hosting a blog for cheap and lazy devs
31–40 of 74 posts
Re: Self-hosting a blog for cheap and lazy devs
#32I migrated away from Wordpress to github pages and Jekyll... https://wade.be/2016/01/30/welcome-to-jekyll.html Can’t get any easier, cheaper or lazier than that.
> Wordpress is bloated. It won’t even run on a basic free DigitalOcean instance.
Woah, does it use an obscene amount of RAM or what? It's been a while since I used it. (Also, I think you meant the cheapest Droplet using the free $100 credit? I don't think there is a free tier. Would be nice tho :)
Re: Self-hosting a blog for cheap and lazy devs
#33We 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…
All sounds good apart from GoDaddy. Why not use a more reputable registrar? https://news.ycombinator.com/item?id=4362478
Just because it's what we already used. It's the most dispensable part of the stack (and arguably shouldn't even be considered part of our stack at all).
Re: Self-hosting a blog for cheap and lazy devs
#34Anything that starts with "Install Docker" will not be cheap or easy
This is exactly how far I got in before my "No fucking way" alarm went off.
If you want to be truly cheap and lazy use github pages (free), static html (maybe with a markdown converter), and Disqus iframes for comments.
Re: Self-hosting a blog for cheap and lazy devs
#35Anything that starts with "Install Docker" will not be cheap or easy
Glad that I wasn't the only one to have alarm bells go off in my head when I read that first step.
There are plenty of other rational options, most people are saying github pages, but I'd like to put forth the NeoCities + Hugo combo as an alternative. It's a bit more complicated than I'd like but it's absurdly easy to modify and make content for once it's set up.
Re: Self-hosting a blog for cheap and lazy devs
#36Earlier quoted context omitted.
GitLab pages is another great option. It has more generous limits than github pages.
but it also isn't self-hosting.
None of these alternative suggestions are. Nor is the blog post suggestion though, they're not running on their own server but a cloud providers. Sooo all of this is really not self hosted
Re: Self-hosting a blog for cheap and lazy devs
#37This 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.
Re: Self-hosting a blog for cheap and lazy devs
#38Anything that starts with "Install Docker" will not be cheap or easy
This is exactly how far I got in before my "No fucking way" alarm went off. If you want to be truly cheap and lazy use github pages (free), static html (maybe with a markdown converter), and Disqus iframes for comments.
Ding ding ding, we have a winner! This is exactly the process I landed on this week when I decided to start a blog. There's literally nothing cheaper or more convenient (or resume-appropriate, since I already share my github) than github pages. Generating a static site is almost trivial (I landed on using Hugo, but a bunch of solutions are just as easy).
To take the laziness a step further I use emacs and org-mode and publish with ox-hugo (https://ox-hugo.scripter.co/). Set up an org-capture for the blog template, and I'm only a few keystrokes away from creating and publishing a new post at any time.
Re: Self-hosting a blog for cheap and lazy devs
#39The guide exposes the back-end webserver to the public, by accident. Instead of: ports: - "2368:2368" expose: - "2368" The author probably just needs: ports: - 127.0.0.1:2368:2368 That way "localhost:2368" will be routed to 2368 inside the container, such that caddy can access it, but not accessible externally, as it is right now: $ curl -v https://sphuff.com:2368 Though of course the ideal solution would be to run c…
I see this a lot with redis in docker compose as well. I've even done it by mistake.
Also why the heck doesn't redis have auth by default. It's so ridiculously easy to get "hacked" and inadvertently run a crypto miner.
Re: Self-hosting a blog for cheap and lazy devs
#40Also if y'all are looking for incredibly cheap servers https://www.serverhunter.com/ has many listed that are less than $5 a year. Most of them are OpenVZ based, and very low performance but good for hobby projects. The other compromise is many don't have entire IPv4 addresses, just a few forwarded ports.