-
Notifications
You must be signed in to change notification settings - Fork 55
Cannot run in development during image creation, then in production for deployment #94
Comments
|
I can't seem to get this to use development:
Seems like it should work according to --> https://github.com/bucharest-gold/centos7-s2i-nodejs/blob/master/s2i/env |
This is what I've tried: |
Not to long ago i added something to nodeshift to add env vars to your build config, This is what my build config looks like(edited down)
That makes the build phase install dev dependencies. Looking at where you have your env vars in your build config, i think they might be in the wrong spot? I haven't actually tried to do development mode for builds, prod for deploy. it might work? |
continuing the other comment, to do developemnt build, production deploy, i guess you would need env vars set for both the build Config and deployment config, but i haven't actually tried that yet. (looks like i need to also add something to nodeshift to do this, if this is a workflow people need) |
Looks like yaml is screweing me up.... indentation. Let me try something. |
Okay, yes, my DC and BC YAML indentation was botched. Adding env: vars here to DeploymentConfig and BuildConfig works as it should. Closing. |
|
So, it currently seems like there is no way to run in "development" NODE_ENV during a build, then to run in "production" NODE_ENV when the image is actually deployed.
The BuildConfig NODE_ENV doesn't seem to get picked up.
The text was updated successfully, but these errors were encountered: