Marco Rogers

I forgot to mention that I also set up automated database migration systems in my personal projects. I’m such weirdo.
@bo_brinkman@kind.social

@davatron5000@mastodon.social huh. Most of this stuff I don't worry about at all for small projects. A good pass will handle security sandboxing between the app and database. Small app means connection limits and caching are a yagni problem. Etc. If these issues feel like barriers to people (again, specifically talking about small software), then I'd like to address that in some way.

I asked this question the other day and I promised to leave some of my own thoughts.

In general, I prefer to move towards automation and push-button deploys sooner rather than later. For my least several projects, I've introduced docker and github actions way sooner than most people would or a personal project. I like a good PaaS system that allows me to just chuck a package at it and set how many nodes I want. Right now fly.io is my goto.
@polotek@social.polotek.net

@KatS@chaosfem.tw what’s funny is that a lot of people, including me, tend to run the docker build at deploy time. Which reintroduces some of the potential dependency drift issues. I’d like to be using the docker image as the actual deploy artifact, but for many cloud solutions, that ends up being the less convenient approach. It’s weird.