You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This solution was originally designed with the idea that customers with multiple environments would run a dedicated installer repo for each environment (i.e. a repo for DEV, and another for PROD).
This approach worked for some customers, but did not align with other implementations where the client team wanted to manage all of their deployments out of a single repo.
We should consider retrofitting the project structure to allow 2+ deployments to be run out of a single repo instance.
The text was updated successfully, but these errors were encountered:
This solution was originally designed with the idea that customers with multiple environments would run a dedicated installer repo for each environment (i.e. a repo for DEV, and another for PROD).
This approach worked for some customers, but did not align with other implementations where the client team wanted to manage all of their deployments out of a single repo.
We should consider retrofitting the project structure to allow 2+ deployments to be run out of a single repo instance.
The text was updated successfully, but these errors were encountered: