Open JacobEvelyn opened 1 year ago
Ahh. I didn't understand the request fully. I see and understand it. I'm not sure how to gate or guard this logic though. A simple solution would be to add an escape valve-like env var check like HEROKU_SKIP_DATABASE_YML_WRITE=1
Would something like that work for you?
That probably would work, but we've actually migrated off of Heroku so I personally am less invested in this issue.
I previously opened #1278 for this issue and I'm not sure why it was closed. This buildpack overwrites our
config/database.yml
unless we haveactiverecord
in ourGemfile
, but we don't actually useactiverecord
(we use thesequel
gem instead, which also usesconfig/database.yml
). Is there a way this buildpack can allow us to removeactiverecord
from ourGemfile
without overwriting ourconfig/database.yml
file?Requiring a gem we don't need is annoying, slows down our
bundle install
times, and increases our surface area for security vulnerabilities.