I had a good experience with go-bindata and sql-migrate. Recently I switched to https://github.com/rakyll/statik for a number of reasons. To get statik and sql-migrate to work I did the following (note that I use latest master to get the name-spacing feature):
I wonder if the issue is on statik side or sql-migrate. A quick upstream fix would be to just prefix the info.Name() in findMigrations() with a /. But I can't tell if this will affect others.
I had a good experience with
go-bindata
andsql-migrate
. Recently I switched to https://github.com/rakyll/statik for a number of reasons. To getstatik
andsql-migrate
to work I did the following (note that I use latest master to get the name-spacing feature):But migrating fails with
Error while opening 000_my_migration.sql: file does not exist
.I double checked and the file is there. So I tried to open it:
And it failed to!
To get this working, I had to prefix the filename with a
/
;I wonder if the issue is on
statik
side orsql-migrate
. A quick upstream fix would be to just prefix theinfo.Name()
infindMigrations()
with a/
. But I can't tell if this will affect others.