As some of you are aware, I contemplated switching to a static site yesterday. That thought has been slung from the window at a rapid rate. Here's my completely unqualified rant:
https://ttmd.grayw.co.uk/a-static-u-turn/
Thank you to everyone who took the time to send me their thoughts and suggestions.
@gray Good read :) I went over to Hugo, but in my case chose to cut out the Git stuff and complexity. Instead I'm syncing the whole content folder to my various workstations and phone with Resilio Sync. For my needs, it keeps a 30 day history of file changes, if I make a mistake, and I set up a dirty cron job that just runs the hugo build task on the VPS twice a day. So I update a content post on my phone, it syncs up, and a few hours later posts live.
@techzerker That's a pretty cool method of working it.
Interesting that you're still publishing it up behind Nginx though. At that point I'd find it quicker to go my existing route.
I love how we all get to the same results from very different paths.
Thank you so much for taking the time to read my post!
@gray Thanks! Aye, in this case its just behind nginx because the same VPS runs my Miniflux RSS, Subsonic Server, and a few other products that nginx helps with subdomain routing, so it was easiest to keep it consistent even though its not necessary for the static site.
@gray Before that, I had researched the same rabbit hole of Git repos, CI/CD Deployment, Forestry and all that complexity, but it was way more than what I needed or wanted. So now it uses the process I described, on my VPS with my existing Nginx reverse proxy sitting infront of it.