Closed drnic closed 6 years ago
@drnic you missed an important step to repo this; you have to be using dep
, see the script below. Now that I can repo, I should be able to fix.
FROM gobuffalo/buffalo:latest
RUN mkdir -p $GOPATH/src/github.com/markbates
WORKDIR $GOPATH/src/github.com/markbates
RUN buffalo new --skip-webpack coke --db-type=sqlite3
WORKDIR $GOPATH/src/github.com/markbates/coke
RUN buffalo db create -a -d
RUN buffalo g resource widget name
RUN buffalo b -d
# works fine:
RUN ./bin/coke migrate
RUN buffalo db drop -a -d
RUN buffalo db create -a -d
RUN dep init -v
RUN buffalo b -d
# fails
RUN ./bin/coke migrate
Update: The fix for this is here https://github.com/gobuffalo/pop/pull/130
@drnic the temporary work around, until that PR is merged, is to use the following in your Gopkg.toml
:
[[constraint]]
name = "github.com/gobuffalo/pop"
branch = "fizz-less"
@drnic fixed with the release of pop v4.5.11
https://github.com/gobuffalo/pop/releases/tag/v4.5.11. Update your dependencies and you'll be good to go.
In production there is no dep nor buffalo, there is only the coke
CLI. Are you saying I need my git repo, dep
and buffalo
CLIs in production to use Buffalo? Actually, I'm not sure what the "missed an important step" is in the example above.
Will try upgrading pop.
No, you don’t need all that. I assumed you were using dep because the output you pasted from buffalo shows dep information.
Ah gotcha.
Upgraded to pop 4.5.11 and it works; hurray!
Yay! Sorry about all that. That anko package, and it’s maintainer, have been hard to deal with. Thankfully it’s gone now. On Jun 27, 2018, 6:36 PM -0400, Dr Nic Williams notifications@github.com, wrote:
Ah gotcha. Upgraded to pop 4.5.11 and it works; hurray! — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
This issue is a recreation of #1123 which was closed but fix did not turn out to fix issue for me.
Steps to Reproduce the Problem
Please describe in painful detail what you did (so others can play along with you) to get to this point. This includes things like the exact command(s) you used, or the
curl
command you used, that sort of thing.buffalo create -a && buffalo db migrate
works as expected and the app runs finebuffalo drop -a && buffalo build && bin/buffalo_testapp migrate
failsExpected Behavior
Migrations should have run.
Actual Behavior
Info