Closed tobiashienzsch closed 5 years ago
This should be the same bug as #28, which was fixed in #29
buffalo-auth
since didn't get a version bump, which is why go get
still fetches the old version without the fix.
If you're using go modules, running go get -u github.com/gobuffalo/buffalo-auth@754fd3d
should work as a quick workaround.
I'll test this again and hope to be able to push the version to 1.0.4 soon.
I’ll push a release today. On Jan 17, 2019, 8:44 AM -0500, Lukas Schlüter notifications@github.com, wrote:
This should be the same bug as #28, which was fixed in #29 buffalo-auth since didn't get a version bump, which is why go get still fetches the old version without the fix. If you're using go modules, running go get -u github.com/gobuffalo/buffalo-auth@754fd3d should work as a quick workaround. I'll test this again and hope to be able to push the version to 1.0.4 soon. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
released.
Mark Bates On Jan 17, 2019, 8:44 AM -0500, Lukas Schlüter notifications@github.com, wrote:
This should be the same bug as #28, which was fixed in #29 buffalo-auth since didn't get a version bump, which is why go get still fetches the old version without the fix. If you're using go modules, running go get -u github.com/gobuffalo/buffalo-auth@754fd3d should work as a quick workaround. I'll test this again and hope to be able to push the version to 1.0.4 soon. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
This should be fixed with the release, please reopen if you still have the issue.
Hi,
I created a completely empty buffalo project using version v0.13.12. I then followed the guide for buffalo-auth, so:
No problems here. I then tried to migrate the database with:
The error I got was:
I checked, no table "users" was created, when starting the Dev server I get a 500 response.
I'm running PostgreSQL latest inside docker, any ideas what the problem could be?
Thanks, Toby