krok VS sql-migrate

Booting up a database in a container is relatively fast now-a-days. Take a look here: https://github.com/krok-o/krok/blob/main/tests/livestore/init_test.go

An example for this you can find here: https://github.com/krok-o/krok/tree/main/pkg/krok/providers/handlers

Tests!!! You have none. :) If you want to test with a real DB instead of mocking everything you can do that with an ephemeral container that spins up relatively fast. Here is an example for that: https://github.com/krok-o/krok/blob/main/tests/livestore/init_test.go ( This might be a bit over your head depending on your experience maybe this post is better: https://docs.docker.com/language/golang/run-tests/ )

As others suggested, using the API is nicer. If you are looking for a nice example on how to do that take a look at my docker container executor code here: https://github.com/krok-o/krok/blob/main/pkg/krok/providers/executor/in_memory_executor.go :)

Here is an app where I'm using swagger and I create API documentation by using swagger generator and comments: https://github.com/krok-o/krok

I would like to present a project I've been working on for 1.5 years or so, called Krok Github, Krok Website.

Here is a fairly complex project which does just this: https://github.com/krok-o/krok

Adding to the other comments, this is how Krok uses swagger:

This creates a temporary database in a docker container while you are running your test. For an example look here: https://github.com/krok-o/krok/blob/main/tests/livestore/init_test.go

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.