Self-hosting a blog for cheap and lazy devs
1–10 of 74 posts
Re: Self-hosting a blog for cheap and lazy devs
#2Re: Self-hosting a blog for cheap and lazy devs
#3And if the author is reading - your Author link is broken.
Re: Self-hosting a blog for cheap and lazy devs
#4- 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.
Re: Self-hosting a blog for cheap and lazy devs
#5Re: Self-hosting a blog for cheap and lazy devs
#6Re: Self-hosting a blog for cheap and lazy devs
#7Re: Self-hosting a blog for cheap and lazy devs
#8Re: Self-hosting a blog for cheap and lazy devs
#9This 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.
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.
Re: Self-hosting a blog for cheap and lazy devs
#10Instead 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 caddy as another container, and link them together.