Skip to content
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

Add different configuration settings for different environments #12

Closed
lecaillon opened this issue Jul 15, 2017 · 0 comments
Closed

Add different configuration settings for different environments #12

lecaillon opened this issue Jul 15, 2017 · 0 comments
Assignees
Milestone

Comments

@lecaillon
Copy link
Owner

lecaillon commented Jul 15, 2017

Motivation:

Actually Evolve does not support different configuration for different environments for .NET Core projects.
It only uses a simple json file called Evolve.js for it.
Not ideal when you want to have different setup between Development, Staging and Production.

Solution:

Allow to specfiy multiple configuration files merged at build-time by Evolve depending the selected build configuration. A little like the appsettings.json file behavior.

Exemple:

2 configurations files:

  • Evolve.js
  • Evolve.Staging.js

Assuming you've created a specfic build configuration called Staging, the result will be:

  • In Debug configuration mode, only the Evolve.js file is loaded by Evolve.
  • In Staging configuration mode, the Evolve.js file will be loaded first and then, will be overriden by the Evolve.Staging.js file.
@lecaillon lecaillon self-assigned this Jul 15, 2017
@lecaillon lecaillon added this to the Evolve 1.4.0 milestone Jul 15, 2017
@lecaillon lecaillon changed the title Add appsettings.json support for .NET Core projects Add different configuration settings for different environments Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant