Closed ghost closed 7 years ago
I'm unable to reproduce this in a brand new docker image (although it's possible the fix for #1681 also fixed this). Let us know if this is still a problem.
Could you please provide some details on the docker image environment? In the meantime I will try the manual steps described in #1681
I used the ruby:latest
image, installed the rails gem and nodejs runtime, and ran the template installer command as documented in the README.
Thank you
Sorry to bother you with this, but I still can't seem to find the cause of the problem. I tried switching from centos 7.2 to oracle linux 7 and tried switching rvm with rbenv. Still the exact same error. Could you by any chance provide the details of your deployed environment? Such as gem versions and os.
It looks like its eager loading, which is odd for a generator running in development mode. Are you setting the RAILS_ENV
environment variable?
Yes, to 'production'. We have developed a chef cookbook. It was working well and passing kitchen tests last Wednesday. Thursday morning, without any changes to the cookbook or the branch being deployed, this error started to occur.
Generators are intended to be run only in development mode. Then you commit the generated code, and then deploy what you have in version control.
Interesting. That explains a lot. Thank you.
You may have inferred this, but we are new to Ruby on Rails. Primarily a Java shop.
This began occurring late last week. Have tried several attempts at deploying under different conditions. Always with the same results: