Wojciech Wnętrzak
Wojciech Wnętrzak
By default kamal builds image from the git commited files only, so you would need to change the build context to make it work this way. https://kamal-deploy.org/docs/configuration/builder-examples/#using-a-different-dockerfile-or-context-when-building
> And also, you wouldn't want the secret files to be bundled into the image. That's true. Other solution would be to copy the file to the host server (one...
@igor-alexandrov Looks like this was done in https://github.com/basecamp/kamal/pull/924/files#diff-7c2750e7045b7ddc6644f16f09b6690ad88e45b73bf747e14a1a0bf563c0f156R18
Thank you for this. This will greatly simplify migration to kamal on existing projects.
BTW, I see that Ostruct is not used anywhere in the code so maybe the "require" can be removed? https://github.com/search?q=repo%3Arollbar%2Frollbar-gem%20Ostruct&type=code
I second that question. I didn't try yet the new reporter integration, but wouldn't the error be double submitted with the middleware and Active Job plugin enabled?
It now raises the error with recently released rack 3.2, so authlogic is not compatible with it https://github.com/rack/rack/pull/2193
Not stale. Still wondering if it was intended
Since the proposed PR was closed, this can be closed as well @hyprhex ?
@rafaelfranca As spoken on Rails World, I tested this in my app and it works for my usecase. To make it work flawlessly with my form objects (just simple ActiveModel::Model...