Feature #61503

Set deploymentPath on a per node-base

Added by Johannes Steu almost 7 years ago. Updated over 5 years ago.

Status:
Accepted
Priority:
Should have
Assignee:
-
Target version:
-
Start date:
2014-09-10
Due date:
% Done:

0%

Estimated time:

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.

#1

Updated by Christopher Hlubek over 6 years 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 over 6 years ago

  • Status changed from New to Accepted
#3

Updated by Christopher Hlubek over 6 years ago

  • Status changed from Accepted to New
#4

Updated by Helmut Hummel over 5 years ago

  • Status changed from New to Accepted

Development of TYPO3 Surf now moved to Github. If you think this is still relevant, please open a bug report or feature request here:

https://github.com/TYPO3/Surf

Also available in: Atom PDF