Bug #62319
Enhance Task SymlinkConfigurationTask to use not only the Production context
Status: | Resolved | Start date: | 2014-10-18 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
For deployment i'd like to use the SymlinkConfigurationTask for all Contexts.
If you deploy your Application on different Nodes and run an separate testing Builds the Configuration could be stored in shared/Configuration/Testing. Same for the Development Context for Develop-Builds.
Therefore the SymlinkConfigurationTask could use $application->getContext().
History
#1 Updated by Johannes Steu 10 months ago
An implementation could look like this
$targetReleasePath = $deployment->getApplicationReleasePath($application);
$context = $application->getContext();
if($context === NULL || $context == "") {
throw new \TYPO3\Surf\Exception\InvalidConfigurationException("No context is configured");
}
$commands = array(
"cd {$targetReleasePath}/Configuration",
"rm Rf ".$context."/*",
"if [ -d ".$context." ]; then rmdir ".$context."; fi",
"mkdir -p ../../../shared/Configuration/".$context,
"ln -snf ../../../shared/Configuration/".$context." ".$context
);
$this>shell->executeOrSimulate($commands, $node, $deployment);
#2 Updated by Christopher Hlubek 6 months ago
- Status changed from New to Resolved
This is fixed with https://review.typo3.org/#/c/33970/