-
Notifications
You must be signed in to change notification settings - Fork 2.2k
ng deploy - allow configuration for serverTarget #2764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This issue does not seem to follow the issue template. Make sure you provide all the required information. |
As explained here :
|
@geromegrignon Have you looked at my "deploy": {
"builder": "@angular/fire:deploy",
"options": {
"ssr": true,
"functionsNodeVersion": 12
},
"configurations": {
"production": {
"buildTarget": "my-app:build:production",
"serverTarget": "my-app:server:production"
},
"development": {
"buildTarget": "my-app:build:development",
"serverTarget": "my-app:server:development"
}
}
}, I use |
Indeed, i was so focused to look at the codebase i forgot this part of your explanation. |
We're having the exact same use case and would love to get support for this. In our case we have multiple sites with different environment files and need to change them on the server build as well. |
|
Going to keep as open, as I may consider changing this in the upcoming major. |
7.1.0-rc.0 now has serverTarget |
Version info
Angular: 11.0.0
Firebase: 8.1.2
AngularFire: 6.1.4
Node: 14
How to reproduce these conditions
I have two environment configs for my Angular Universal app:
dev.environment.ts
andprod.environment.ts
with different API keys. I configured my entireangular.json
for these two build configurationsproduction
anddevelopment
. However, when I runng deploy --configuration development
the browser build uses the correct configuration, but the server build uses theproduction
config.Steps to set up and reproduce
Expected behavior
Use correct environment for both the browser- and the server build.
Actual behavior
The browser build uses the correct config from the
dev.environment.ts
, but the server build uses theprod.environment.ts
.The text was updated successfully, but these errors were encountered: