Instead of:
ports:
- "2368:2368"
expose:
- "2368"
ports:
- 127.0.0.1:2368:2368
$ curl -v https://sphuff.com:2368
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.
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.
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.
But yeah, zero running code is a really great thing.
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.
And if the author is reading - your Author link is broken.
Netlify, Firebase Hosting, GitHub pages, etc, all make it super easy to host a static blog for free, require zero maintenance, and are all backed by global CDNs.
My blog setup uses Netlify to automatically build and deploy on a git push using the built in Hugo support.
Now of course, there is the argument of what "self-hosting" is. Does it just mean you own your domain name and content? Or does it mean you are actually running the server? If its the latter, then sure this is a valid solution, but if all you care about is owning your domain and content I'd use one of the static hosting providers.
The truly cheap would go with one of them and avoid the $2.50 monthly fee for a server.
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.
I have some notes on how I played with it a couple years ago. https://www.growthalytics.com/programming/2015/07/19/setting...
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?
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.
- 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 of custom CSS.
- Git for storing our content
- Gitlab for CI/CD and hosting
- GoDaddy for domain management
We manage all of the content in Git, and push it when it's ready. It's really easy. You can even run "code reviews" on posts if you like.
https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosti...
I couldn't be happier with the setup: it's cheap, fast, requires zero maintenance and pretty much never goes down. Cost is close to nil: the most expensive part is for Route53 at $0.50 per Hosted Zone, and then S3+CloudFront add a few cents more.
If folks want to see how fast static pages can be on a CDN, the site is at https://re.kv.io
P.S. I didn't have to install Docker or MySQL.
I'm not sure how you got this bill, none of these numbers are anywhere near $80.
That said, I can still count 9 occurrences of degraded performance for a total of 16 hours and 40 minutes in the past 90 days for GitHub pages on https://www.githubstatus.com/ – as a matter of fact performance is shown as degraded right now. That's pretty terrible.
Perhaps I'm missing something, but I don't get why these articles pop up so frequently as if making a blog was some super complicated thing that required the latest CMS, etc. Most people here (including me) would suffice with a nginx and plain html/css, no CMS required, based on articles like these, at least.
[0] https://github.com/sfttw/avanti [1] https://blog.sailingfasterthanthewind.com/
I previously used the S3 + Cloudfront setup that many commenters have mentioned, but have switched to Netlify for static sites simply because I don’t have the overhead of setting up any configuration in AWS. With Netlify, you can be up and running with a new static site as soon as the DNS record propagates.
I’ve always wondered if there was any throttling or performance impact at high traffic- but I haven’t built any high-traffic sites yet :)
Anyone recommending S3, github pages etc hasn't tried Netlify.
Doesn't seem to be much point in competing against $0, though the technical side is interesting.
How readable are these mobile layouts for everybody else?
https://wade.be/2016/01/30/welcome-to-jekyll.html
Can’t get any easier, cheaper or lazier than that.
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 :)
In this case shared hosting will be even cheaper and maintenance free. System, server, Let's encrypt cert, database and language updates will be taken care of. Many of those PHP CMS-es or blogging systems have a one click updates in place. Some shared hosting providers can also take care of this for you. You can get something with ssh access and rsync so you can be lazy and edit HTML with Word and just sync it or an SSG if that strikes your fancy.
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.