Rails Issues with Buildpacks #413
Unanswered
eric-hemasystems
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm hoping this is the right place to ask this. I've got a Rails app using the older runtimes (based on Ubuntu 16) prior to the introduction of the buildpacks. My app needs a few libraries installed which previously were installed via the
runtime_config.packages
key in theapp.yaml
file.There are a handful of libraries that come pre-packaged with the new runtime but the docs basically say if you need anything more than that you have to use a custom runtime and build your own Dockerfile.
But then this page explains a bit of how to maybe extend the GAE runtime with additional packages instead of making my own Dockerfile from scratch which looks appealing. I have worked at it a good bit and it's almost going. The two issues I have noticed are:
Missing
libpq-dev
This is one of the default libraries listed on the default runtime doesn't seem to be already installed if I build my own from
gcr.io/buildpacks/builder:google-22
. Is that expected? It's not a big deal as I can just addlibpq-dev
with my own packages I'm installing and it seems to work. But it made me wonder if I'm building fro the right base image.assets:precompile
Is Always in Production EnvThe bigger issue is when my assets are pre-compiled it fails because the RAILS_MASTER_KEY doesn't match with the following error:
The reason for the mismatch is this is not my production environment because it is my staging env. I have tried passing
-e RAILS_ENV=staging
topack build
but no luck. I believe here it seems to be hard-coded to the production env and I don't see how to override.Also I find it wild that it continues with the build even though the assets failed. I would have expected it to break the build.
Beta Was this translation helpful? Give feedback.
All reactions