service VS sql-migrate

I've got my own super simple service template that I use internally for this: https://github.com/maragudk/service . I don't think I've added HTMX here (because I add it when needed), but it has auth and is totally classic in its setup.

I do something similar in https://github.com/maragudk/service with SQLite, feel free to have a look. 😊

I’m biased towards my own HTML component library called gomponents, but here’s an example of how I use that with Tailwind: https://github.com/maragudk/service

I'd never did this with sqlite3, but I think sql-migrate should work (https://github.com/rubenv/sql-migrate)

I use sqlboiler which generates an ORM from your database, and sql-migrate which is a tool for managing SQL migrations. Although you have to write your migrations in SQL, which IMHO is a plus.

Currently a fan of this one https://github.com/rubenv/sql-migrate

db migration by sql-migrate

There are some packages in my project that are not used in the source code, but they're used as commands (i.e. https://github.com/vektra/mockery https://github.com/rubenv/sql-migrate).

Keep your migrations in the code repo and use a tool like sql-migrate to automatically apply them for you. At my job, we run a new container for each package's tests, and create a new db with the migration scripts for every test. It's certainly a bit slower, but the reproducibility is worth it.