A development server and production to configure the server properly After
I know two different perspectives:
/ P> P> A The first option is by modifying the version parameter. Version: App-Steiging
What do I not like about this approach that the production data is polluted with my scaffolding tests (correct me if I
- Staging Version and Production Version
-
-
Staging Version and Production Edition share the same log
About the first point, I do not know if it is fixed using "New" Could ".
B. Another option is by modifying the Application parameter. R
Applications: With this approach,
, I will create a second application entirely independently from the production version.
I see that the only drawback is that I have been forced to configure a second app (Admin Setup).
Like this solution works well with a backup \ restoration tool as well.
What type of approach are you using to establish a lofted environment for your web application?
Also, do you have any automated script to replace Yamalt before deployment?
I chose the second option in my set-up, because it was the fastest solution, and I still have No script has been created to change application-parameters on deployment.
But the way I'm looking at it, option is a cleaner solution. You can switch the datestore namespace based on the version with some code lines, which you can get from the environment variable CURRENT_VERSION_ID here dynamically. Can:
Comments
Post a Comment