MsDeploy : how to have many productions environment
Today, I have a production environment hosted on IIS and using MsDeploy to be deployed. So the database connection string is set in appsetting.Production.json.
But i have to make a second production environment. So i will create a new publish profile for this environment but how can i set the connection string for this new environment ?
Thanks in advance,
asp.net-core .net-core asp.net-core-mvc msdeploy
add a comment |
Today, I have a production environment hosted on IIS and using MsDeploy to be deployed. So the database connection string is set in appsetting.Production.json.
But i have to make a second production environment. So i will create a new publish profile for this environment but how can i set the connection string for this new environment ?
Thanks in advance,
asp.net-core .net-core asp.net-core-mvc msdeploy
add a comment |
Today, I have a production environment hosted on IIS and using MsDeploy to be deployed. So the database connection string is set in appsetting.Production.json.
But i have to make a second production environment. So i will create a new publish profile for this environment but how can i set the connection string for this new environment ?
Thanks in advance,
asp.net-core .net-core asp.net-core-mvc msdeploy
Today, I have a production environment hosted on IIS and using MsDeploy to be deployed. So the database connection string is set in appsetting.Production.json.
But i have to make a second production environment. So i will create a new publish profile for this environment but how can i set the connection string for this new environment ?
Thanks in advance,
asp.net-core .net-core asp.net-core-mvc msdeploy
asp.net-core .net-core asp.net-core-mvc msdeploy
asked Nov 12 '18 at 20:45
Fabien Dezautez
366
366
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Are they being deployed to separate machines? You can override the settings in appsettings.json
by using Environment settings. You don't need to change your code to do this as ASP.NET Core does all the work for you.
In short, settings are read in the following order, with the later ones overriding values from the earlier ones:
- Files (appsettings.json, appsettings.Environment.json, where
Environment is the app's current hosting environment) - Azure Key Vault
- User secrets (Secret Manager) (in the Development environment only)
- Environment variables
- Command-line arguments
So, on your second production machine you can add an Environment variable
to override the setting in appsettings.Production.json
.
If you are using SQL Server then you can set the SQLCONNSTR_
environment variable to override your setting, add your connection name at the end e.g. SQLCONNSTR_DefaultConnection
.
If you are going to use environment variables to override the settings on one machine I suggest you do it for all production machines for consistency.
Take a look at this section in the Configuration in ASP.NET Core for the full configuration sequence.
Information regarding the specific ConnectionString
settings are on the same page as above.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269843%2fmsdeploy-how-to-have-many-productions-environment%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Are they being deployed to separate machines? You can override the settings in appsettings.json
by using Environment settings. You don't need to change your code to do this as ASP.NET Core does all the work for you.
In short, settings are read in the following order, with the later ones overriding values from the earlier ones:
- Files (appsettings.json, appsettings.Environment.json, where
Environment is the app's current hosting environment) - Azure Key Vault
- User secrets (Secret Manager) (in the Development environment only)
- Environment variables
- Command-line arguments
So, on your second production machine you can add an Environment variable
to override the setting in appsettings.Production.json
.
If you are using SQL Server then you can set the SQLCONNSTR_
environment variable to override your setting, add your connection name at the end e.g. SQLCONNSTR_DefaultConnection
.
If you are going to use environment variables to override the settings on one machine I suggest you do it for all production machines for consistency.
Take a look at this section in the Configuration in ASP.NET Core for the full configuration sequence.
Information regarding the specific ConnectionString
settings are on the same page as above.
add a comment |
Are they being deployed to separate machines? You can override the settings in appsettings.json
by using Environment settings. You don't need to change your code to do this as ASP.NET Core does all the work for you.
In short, settings are read in the following order, with the later ones overriding values from the earlier ones:
- Files (appsettings.json, appsettings.Environment.json, where
Environment is the app's current hosting environment) - Azure Key Vault
- User secrets (Secret Manager) (in the Development environment only)
- Environment variables
- Command-line arguments
So, on your second production machine you can add an Environment variable
to override the setting in appsettings.Production.json
.
If you are using SQL Server then you can set the SQLCONNSTR_
environment variable to override your setting, add your connection name at the end e.g. SQLCONNSTR_DefaultConnection
.
If you are going to use environment variables to override the settings on one machine I suggest you do it for all production machines for consistency.
Take a look at this section in the Configuration in ASP.NET Core for the full configuration sequence.
Information regarding the specific ConnectionString
settings are on the same page as above.
add a comment |
Are they being deployed to separate machines? You can override the settings in appsettings.json
by using Environment settings. You don't need to change your code to do this as ASP.NET Core does all the work for you.
In short, settings are read in the following order, with the later ones overriding values from the earlier ones:
- Files (appsettings.json, appsettings.Environment.json, where
Environment is the app's current hosting environment) - Azure Key Vault
- User secrets (Secret Manager) (in the Development environment only)
- Environment variables
- Command-line arguments
So, on your second production machine you can add an Environment variable
to override the setting in appsettings.Production.json
.
If you are using SQL Server then you can set the SQLCONNSTR_
environment variable to override your setting, add your connection name at the end e.g. SQLCONNSTR_DefaultConnection
.
If you are going to use environment variables to override the settings on one machine I suggest you do it for all production machines for consistency.
Take a look at this section in the Configuration in ASP.NET Core for the full configuration sequence.
Information regarding the specific ConnectionString
settings are on the same page as above.
Are they being deployed to separate machines? You can override the settings in appsettings.json
by using Environment settings. You don't need to change your code to do this as ASP.NET Core does all the work for you.
In short, settings are read in the following order, with the later ones overriding values from the earlier ones:
- Files (appsettings.json, appsettings.Environment.json, where
Environment is the app's current hosting environment) - Azure Key Vault
- User secrets (Secret Manager) (in the Development environment only)
- Environment variables
- Command-line arguments
So, on your second production machine you can add an Environment variable
to override the setting in appsettings.Production.json
.
If you are using SQL Server then you can set the SQLCONNSTR_
environment variable to override your setting, add your connection name at the end e.g. SQLCONNSTR_DefaultConnection
.
If you are going to use environment variables to override the settings on one machine I suggest you do it for all production machines for consistency.
Take a look at this section in the Configuration in ASP.NET Core for the full configuration sequence.
Information regarding the specific ConnectionString
settings are on the same page as above.
answered Nov 13 '18 at 0:07
Simply Ged
2,32821121
2,32821121
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269843%2fmsdeploy-how-to-have-many-productions-environment%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown