Feature #61503
Set deploymentPath on a per node-base
| Status: | New | Start date: | 2014-09-10 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
If you would like to deploy one application on two different nodes both nodes are using the same deployment path. But if your nodes run a different / setup the path does not fit on both nodes. For example node1 runs their webs under /var/www and node2 under /srv/www you would have create 2 applications with two nodes.
It would be cool to set a deploymentPath for each node that overrides the deploymentPath from application if it is set.
History
#1 Updated by Christopher Hlubek 6 months ago
I agree, we should change the deployment path to be just an option that can be set on the deployment, application, node or task level.
For this we need to refactor the handling of the deployment path getter to a merged option (which is planned anyway).
#2 Updated by Christopher Hlubek 6 months ago
- Status changed from New to Accepted
#3 Updated by Christopher Hlubek 6 months ago
- Status changed from Accepted to New