4 ms·
This is 100% possible without a server. Your repo can be your database if you run it statically with something like Hugo (a single binary with no dependencies).
by sgallant 5y ago
This is 100% possible without a server. Your repo can be your database if you run it statically with something like Hugo (a single binary with no dependencies). Store your content in your own repo in Markdown files (or something similar, like MDX) and host it on Netlify, Vercel, AWS, etc.
If your site has 10K posts and you don’t want to deal with long build times, use Next.js with ISR (make some high traffic pages static, others dynamic (server side rendered)).
As the founder of Forestry.io and Tina.io, I’m biased about a content editing UI, but there are many options if you want a GUI on top of your content files.
You got this.
- hanklazard 5y agoAgreed! I’ve used Hugo + Netlify for the last few years, really like it. I’m not a big blogger, but it would be easy to run a blog with this setup.
- sneak 5y agoYou don't need Netlify for this; all you need is a git repo somewhere and CI. CI can do the build, and the last step of CI can be ftp, rsync, scp, or whatever. It's just static files, normal hosting anywhere is fine.
- deleted 5y ago[deleted]
- viraptor 5y agoThere's usually a huge difference in access latency though. The usual cheap ftp hosting means a choice of whether you want to be 200ms away from the US or from Australia.