A simple and flexible database migration tool for Go applications.
To install as a CLI tool:
go install github.com/olbrichattila/godbmigrator_cmd/cmd/migrator@latestIf you'd like to integrate the migration into your application, please refer to: https://github.com/olbrichattila/godbmigrator/
Follow this structure: [id]-migrate-[custom-content].sql
The files are processed in ascending order, so it's important to prefix them with an ID or timestamp.
Alternatively, you can use the following command to generate a properly formatted migration file: migrator add <optional suffix>
For example:
2024-05-27_19_49_38-migrate.sql
2024-05-27_19_49_38-rollback.sql
2024-05-27_19_50_04-migrate.sql
2024-05-27_19_50_04-rollback.sqlMigrate:
migrator migrateRollback:
migrator rollbackReport:
migrator reportAdding new migration and rollback file:
migrator add <your custom message>Note: the custom message is not mandatory, in that case the file will be a standard format, like date_time-migration.sql
You can apply or roll back a specific number of migrations by passing a number as an argument.
Migrate the last 2 migrations:
migrator migrate 2
migrator rollback 2(Refresh is when all applied migration is rolled back and migrated up from scratch)
migrator refreshHere if the count parameter supplied will be ignored
Note: this feature is currently in beta You can create a snapshot of the current database schema and restore it when recreating the database.
This is also useful for generating a test database from a production database without copying data. Please note: this supports only SQLite, MySql and PostgreSQL. (firebird support coming later)
Usage:
migrator save-baseline
migrator restore-baselinemake installThe build folder will contain the migrator executable.
Usage is the same but using the application:
migrator migrate
migrator rollback
migrator migrate 2
migrator migrate 2 -force
migrator rollback 2
migrator refresh
migrator report
migrator validate
migrator save-baseline
migrator restore-baseline
migrator add <optional migration file suffix>
help (for full detailed help)-force This flag will skip checksum verification
The number of rollbacks and migrates are not mandatory. If it is set, for rollbacks it only apply for the last rollback batch Validate checks if any migration file changed since last applied
If no .env.migrator file is present, the application will read environment variables from the operating system.
export DB_CONNECTION=sqlite
export DB_DATABASE=./data/database.sqliteUnset the variables can be done:
unset DB_CONNECTION
unset DB_DATABASEExamples:
Note: TABLE_PREFIX is non mandatory, if not set, the migration table prefix will be olb (example olb_migrations, olb_migration_reports)
DB_CONNECTION=sqlite
DB_DATABASE=./data/database.sqlite
TABLE_PREFIX="my_prefix" # (Optional: Defaults to "olb_")DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=migrator
DB_USERNAME=root
DB_PASSWORD=password
TABLE_PREFIX="my_prefix"DB_CONNECTION=pgsql
DB_HOST=127.0.0.1
DB_PORT=5432
DB_DATABASE=postgres
DB_USERNAME=postgres
DB_PASSWORD=postgres
TABLE_PREFIX="my_prefix"
# non mandatory, it defaults to disable
# possible values are: disable, require, verify-ca, verify-full, prefer, allow (depending on your setup)
DB_SSLMODE=disableDB_CONNECTION=firebird
DB_HOST=127.0.0.1
DB_PORT=3050
DB_DATABASE=/opt/firebird/examples/empbuild/employee.fdb
DB_USERNAME=SYSDBA
DB_PASSWORD=masterkey
TABLE_PREFIX="my_prefix"
MIGRATOR_MIGRATION_PATH=./migrations/firebirdThe path by default is ./migrations This can be overwritten by adding the followin variable to your .env file
MIGRATOR_MIGRATION_PATH=./migrations/custom_pathSet the server port. If not defined, it will default to 8080.
HTTP_SERVER_PORT=8081make migrate
make rollback
make refresh
make install
make reportmake switch-sqlite
make switch-mysql
make switch-pgsql
make switch-firebird# Create your docker containers with docker-compose, MySql, FireBird and Postgresql images will be creted exposing the default ports, Change it if required.
cd docker
docker-compose up -dSwitch to your testable database with the above make switc- command.
Check your .env file for migration path:
MIGRATOR_MIGRATION_PATH=./migrations/newand create a folder if not exists:
mkdir -p ./migrations/newmigrator add <optionally a file name suffix>Fill in your migration and rollback file you created, then try migrate, rollback, (with number parameters) and report as explained above
To run the migrator locally, use:
migrator serveThe following URL parameters can be used:
- command – The migration command (e.g., migrate, rollback).
- count (optional) – Number of items to migrate or rollback.
- force (optional) – Accepts 0, 1, false, or true. Forces migration even if integrity validation fails.
Example Requests
http://localhost:8081?command=migrate&count=2&force=true
http://localhost:8081?command=add&name=add_usersPull the Image
docker pull aolb/migratorRun with Environment Variables
docker run -e HTTP_SERVER_PORT=8080 -e DB_CONNECTION=sqlite -e DB_DATABASE=./database.sqlite -e MIGRATOR_MIGRATION_PATH=./ -p8080:8080 aolb/migratorExample docker compose
version: "3.8"
services:
migrator:
image: aolb/migrator:latest
build: .
ports:
- "8081:8080"
environment:
- HTTP_SERVER_PORT=8080
- DB_CONNECTION=sqlite
- DB_DATABASE=./database.sqlite
- MIGRATOR_MIGRATION_PATH=./
restart: unless-stopped- Learn more about me on my personal website: https://attilaolbrich.co.uk/menu/my-story
- Check out my latest blog post on my website: https://attilaolbrich.co.uk/blog/1/single