Promoting applications from test to production: Difference between revisions
From The Maceys in California
Lynn Macey (talk | contribs) Created page with "==Setting up an application in the test environment== ===Adding and naming stacks=== The purpose of having a test environment is to allow applications to be stood up and tested without disturbing the other applications in the group. I have tried to not add too many additional stacks to the original set, but the author's interests and mine diverge a little bit. Going forward, adding applications to a stack is done by adding a new stack with a number at the end. For exampl..." |
Lynn Macey (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Setting up an application in the test environment== | ==Setting up an application in the test environment== | ||
===Adding and naming stacks=== | ====Adding and naming stacks==== | ||
The purpose of having a test environment is to allow applications to be stood up and tested without disturbing the other applications in the group. I have tried to not add too many additional stacks to the original set, but the author's interests and mine diverge a little bit. Going forward, adding applications to a stack is done by adding a new stack with a number at the end. For example, adding applications to the admin stack is done with a new stack called admin2. An admin3 can be added so that the number of applications in a stack don't become unmanageable. | The purpose of having a test environment is to allow applications to be stood up and tested without disturbing the other applications in the group. I have tried to not add too many additional stacks to the original set, but the author's interests and mine diverge a little bit. Going forward, adding applications to a stack is done by adding a new stack with a number at the end. For example, adding applications to the admin stack is done with a new stack called admin2. An admin3 can be added so that the number of applications in a stack don't become unmanageable. | ||
===Incorporating the docker-compose.yml file into the stack=== | ===Incorporating the docker-compose.yml file into the stack=== | ||
Revision as of 00:19, 10 September 2026
Setting up an application in the test environment
Adding and naming stacks
The purpose of having a test environment is to allow applications to be stood up and tested without disturbing the other applications in the group. I have tried to not add too many additional stacks to the original set, but the author's interests and mine diverge a little bit. Going forward, adding applications to a stack is done by adding a new stack with a number at the end. For example, adding applications to the admin stack is done with a new stack called admin2. An admin3 can be added so that the number of applications in a stack don't become unmanageable.
