Skip to content
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.

The migrate command on a built binary doesn't work #289

Closed
markbates opened this issue Mar 14, 2017 · 6 comments
Closed

The migrate command on a built binary doesn't work #289

markbates opened this issue Mar 14, 2017 · 6 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@markbates
Copy link
Member

After building a binary and trying to run mybin migrate it starts the server instead of running the migrations. This appears to only be broken in 0.8.0.

@markbates markbates added the bug Something isn't working label Mar 14, 2017
@markbates markbates added this to the 0.8.0 milestone Mar 14, 2017
@markbates markbates self-assigned this Mar 14, 2017
@markbates
Copy link
Member Author

Apparently this was just me being stupid. I had an binary of the same name installed and instead of running ./mybin I was running mybin which ran the old binary. Oops. :)

@JamesMura
Copy link

Seem to be having this issue with v0.9.1 is there any way I can debug this, when I run the migrate command all it prints out is "--> Running migrations" and the time it took

@markbates
Copy link
Member Author

There is a big 0.9.1 that broke migrations. Use either 0.9.1.2 or 0.9.2

@JamesMura
Copy link

upgrading the version worked. Thank you

@fdonzello
Copy link
Contributor

Commenting here @markbates since looks like the most appropriate place even if the issue is closed.

I'm using the shipped Dockerfile to run a buffalo app on kubernetes.
Migrations are not executed on pods recreation.

Do you use k8s for buffalo and have any hints?

@markbates
Copy link
Member Author

I don’t use k8s, so I’m the wrong person to ask. Sorry.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants