Is this project dead?

[Former user]

I use it in production, if is dead I will make a fork of it if the author doesn't mind

[Liam Staskawicz]

Apologies, but yes I don't have much availability for this project these days, so would be happy to hand it off, or see it forked.

[Former user]

I will make a fork then, and thanks for you work on this. (:

[Mauricio Leyzaola]

Hi Liam, I am going to fork this repo as well: https://github.com/mauleyzaola/goose. Thanks, it has been of great use for the last year among many projects.

[Geert-Johan Riemer]

It's probably best to pick one of the forks and continue on that. It wouldn't be nice to join efforts instead of splitting. It looks like CloudCom/goose is the most successful fork?

https://github.com/CloudCom/goose

[Mauricio Leyzaola]

Finally I chose this other framework, which is based on goose also: https://github.com/rubenv/sql-migrate Thanks anyway.

[Parker M]

I'm still keeping an eye out for PR's and such that come in. Might just need to update my email preferences so I don't miss anything.

[Vojtech Vitek]

We maintain the following fork on Github: https://github.com/pressly/goose

• No config files
• Default goose binary can migrate SQL files only
• Go migrations:
  • We dropped building Go migrations on-the-fly from .go source files
  • Instead, you can create your own goose binary, import github.com/pressly/goose package and run complex Go migrations with your own *sql.DB connection
  • Each Go migration function is called with *sql.Tx argument - within its own transaction
• The goose pkg is decoupled from the default binary:
  • goose pkg doesn't register any SQL drivers anymore (no driver panic() conflict within your codebase!)
  • goose pkg doesn't have any vendor dependencies anymore

In progress:

• Go migrations as plugins (dynamic .so/.dll libraries)

• Optionally allow migration NOT to run in a transaction