Database migrations. CLI and Golang library.
Go to file
mattes 13acfe3e2e remove searchpath package 2014-08-11 03:48:04 +02:00
driver initial 2014-08-11 03:42:57 +02:00
file initial 2014-08-11 03:42:57 +02:00
migrate initial 2014-08-11 03:42:57 +02:00
.gitignore initial 2014-08-11 03:42:57 +02:00
.travis.yml initial 2014-08-11 03:42:57 +02:00
README.md initial 2014-08-11 03:42:57 +02:00
main.go initial 2014-08-11 03:42:57 +02:00

README.md

migrate

Build Status

migrate can be used as CLI or can be imported into your existing Go code.

Available Drivers

Need another driver? Just implement the Driver interface and open a PR.

Usage from Terminal

# install
go get github.com/mattes/migrate

# create new migration
migrate -url="postgres://user@host:port/database" create

# apply all *up* migrations
migrate -url="postgres://user@host:port/database" up

# apply all *down* migrations
migrate -url="postgres://user@host:port/database" down

# roll back the most recently applied migration, then run it again.
migrate -url="postgres://user@host:port/database" redo

# down and up again
migrate -url="postgres://user@host:port/database" reset

# show current migration version
migrate -url="postgres://user@host:port/database" version

# apply the next n migrations
migrate -url="postgres://user@host:port/database" migrate +1
migrate -url="postgres://user@host:port/database" migrate +2
migrate -url="postgres://user@host:port/database" migrate +n

# apply the *down* migration of the current version 
# and the previous n-1 migrations
migrate -url="postgres://user@host:port/database" migrate -1
migrate -url="postgres://user@host:port/database" migrate -2
migrate -url="postgres://user@host:port/database" migrate -n

migrate looks for migration files in the following directories:

./db/migrations
./migrations
./db

You can explicitly set the search path with -path.

Usage from within Go

See http://godoc.org/github.com/mattes/migrate/migrate

import "github.com/mattes/migrate/migrate"

// optionally set search path
// migrate.SetSearchPath("./location1", "./location2")

migrate.Up("postgres://user@host:port/database")
// ... 
// ... 

Migrations format

./db/migrations/001_initial.up.sql
./db/migrations/001_initial.down.sql

Why two files? This way you could do sth like psql -f ./db/migrations/001_initial.up.sql.

Credits