Hell is being the sys admin at a web hosting company.

You can either pay a web developer to update your fully static site once a year, or you can pay them five times a year to clean up your Wordpress install when it inevitably gets popped because that one mailback form plugin you demanded... you know the one that has never received a single non-spam submission... hasn't been updated in ten years... and also you're too cheap to pay someone to maintain your Wordpress site because "why would I do that the site is finished?"

I know, right, it's not like, like software rots or whatever.

My job requires the whole modern pipeline with Vue front ends, Quarkus services and k8s deployments and it's suitable for what we do in our teams.

But I have dozens of websites I built and am still building today in the way described and it works just as well for me. As a single developer with "simple" websites it's just great to have so little mental load when fixing some small things.

Admittedly I have a small script to upload stuff via ftp (if ssh/rsync is not available), so no FileZilla anymore :)

I, too, settled on a minimalist process for deploying my blog, just build it with a Hugo, copy the files over to a cheap server, and there you go, deployed. It's the right tool for the job (for me).

Or, for that matter, using GitHub Actions to do the final Hugo build and remote deployment when you do a git push.

I thought about that process, too, but it’s more convenient to skip the whole “lots of commits” and GHA loop.

At the moment I’m still mainly fixing and customizing the theme, but I expect that once I actually start blogging instead of fixing the theme and learning Hugo, GitHub actions would make sense again.

Bro, if you want to start blogging, just do it and get rid of all these dev stuff and focus on blogging.

I suggest you use a platform like justblogged.com.

Shameless plug, yes I built it.

Bro, thank you for the plug, though I’m fine with recreational theme tweaking first, then blogging at some point in the future.

> I, too, settled on a minimalist process for deploying my blog, just build it with a Hugo, copy the files over to a cheap server, and there you go, deployed.

Meh. That's over-engineered[1] /s :-)

--------------------

[1] I have a bash script that produces the site from markdown snippets, commits it to a repo and the VPS pulls master periodically.

I still think about the person on Mastodon I saw months ago: "My deployment pipeline is to click FILE->SAVE"

A workflow that sounds a lot better than 99% of what I read goes on in modern web development from comments on HN.

Don't believe all the horror stories on HN are necessarily representative without trying it yourself. People generally came up with these newfangled things for a reason. I personally very much appreciate having CI/CD that deploys my changes every time I push.

Never a git history rewrite after a declined pull request, pure “index.html_previous_3” bliss

and then they wake up and go "oh, aw crap!"