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
Our company currently uses Phing for its Deployment, but we want to change that.
Phing offers the option to use Config Placeholders. We use this option to deploy multiple hosts in our Testing environment. For example, if we deploy a branch named "test-1", the created host will be available under "test-1.testing." and it will have its own database named "test-1".
Does Magallanes support Placeholders for Branches?
The text was updated successfully, but these errors were encountered:
I would like to add: A general approach to placeholders might be even more useful We're using magallanes for quite some while now to handle deployments of our projects. We've got 2 hacky patches internally and one of them might not be necessary with placeholders.
Don't have a good idea at the moment how to add this to magallanes though. maybe in the future...
Our company currently uses Phing for its Deployment, but we want to change that.
Phing offers the option to use Config Placeholders. We use this option to deploy multiple hosts in our Testing environment. For example, if we deploy a branch named "test-1", the created host will be available under "test-1.testing." and it will have its own database named "test-1".
Does Magallanes support Placeholders for Branches?
The text was updated successfully, but these errors were encountered: