annabunches/annabunches.net
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Some final wording changes to post.

Browse Source
This commit is contained in:
Anna Rose 2023-09-13 19:33:38 +00:00
parent 33bafa0218
commit fc50209e99
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
content/posts/2023-09-13-how-i-host.md
View File

@ -46,9 +46,20 @@ I could deploy these sites to a simple webserver over SSH or FTP, but instead I
Using containerization gives me a lot of clean, reproducible configuration; just about everything is configured as code, with very little in the way of state on the webserver itself. I can redeploy these onto a new host with zero loss of content at any time, should the need arise.
Plus, my deploy script can just run an elaborate version of this:
```
docker build
docker push
docker-compose pull
docker-compose up -d
```
Which, for a personal blog, feels like just the right amount of infrastructure to deploy.
I also host several Wordpress instances, most notably [Eruditorum Press](https://www.eruditorumpress.com/). I use some of the same infrastructure tricks, but these sites are largely authored by non-technical users and have a strong need for comments, so the static site solutions above aren't feasible. So Wordpress feels like the right solution there.
### Conclusion
### In Conclusion
Ok, so this was mostly just a rant about website bloat. And it's possible I'm missing obvious solutions or am blowing the problem out of proportion. Maybe I've just gotten tired of websites being slow. But it really feels like we ought to have created something that's both easy to use without technical expertise but also produces clean, fast websites for people with simple use cases.