You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using the docker image, either for interactive purposes or for something like a CI runtime, it is often helpful to override the entrypoint and just run the container using with a shell entrypoint. It would be nice to have the migrate binary linked on the path so it can be executed with migrate rather than /migrate.
Describe the solution you'd like
In order to avoid breaking backwards compatibility the cleanest solution is probably just to link the /migrate binary to /usr/bin in case anyone depends on the file being saved at the current location.
Are there any objections to this or was there a reason to avoid placing the binary on the path to begin with?
The text was updated successfully, but these errors were encountered:
Are there any objections to this or was there a reason to avoid placing the binary on the path to begin with?
No objections. I believe/migrate was used for simplicity. Also, I wouldn't count on a shell being available in the docker image. In the future, we might use a scratch docker image.
Is your feature request related to a problem? Please describe.
When using the docker image, either for interactive purposes or for something like a CI runtime, it is often helpful to override the entrypoint and just run the container using with a shell entrypoint. It would be nice to have the
migrate
binary linked on the path so it can be executed withmigrate
rather than/migrate
.Describe the solution you'd like
In order to avoid breaking backwards compatibility the cleanest solution is probably just to link the
/migrate
binary to/usr/bin
in case anyone depends on the file being saved at the current location.Are there any objections to this or was there a reason to avoid placing the binary on the path to begin with?
The text was updated successfully, but these errors were encountered: