[Flow] Set Sub-Context with TYPO3.Surf

[Aske Ertmann]

Hi David,

We just use $application->setContext('Production/Live'); and not the
defaultContext stuff without any problems.

Could be something else than your context causing the permission issues.
E.g. different web server and cli users without correct umask, which is a
problem in Flow (https://jira.typo3.org/browse/FLOW-275)

Hope it helps.

Cheers,
Aske

On Sun, Jun 21, 2015 at 4:02 PM, David Sporer <david.sporer at gmail.com>
wrote:

> Hi,
>
> I’m trying to deploy a Flow application and want to use Production/Staging
> as Context.
> Means I have folder structure like this:
> Configuration/
>         Production/
>                 Staging/
>                         Settings.yaml
>
> This is working fine if I’m setting the context in my .htaccess file
> (SetEnv FLOW_CONTEXT Production/Staging).
> But if I try to set it in my Surf Deployment definition with either one of
> the following:
> - $application->setContext('Production/Staging');
> - $application->setOption('defaultContext', 'Production/Staging');
>
> I get an error during deployment when typo3.surf:typo3:flow:migrate is
> executed. The error is
> Could not write configuration cache file
> /Configuration/Production/Staging/IncludeCachedConfigurations.php
> which is strange because even if I set permissions to 777 the error occurs.
>
> If I use $application->setOption('defaultContext', 'Production/Staging‘);
> the error is
> PHP Fatal error:  Call to undefined method
> TYPO3\Flow\Core\Bootstrap::getEnvironmentConfigurationSetting() in
> /releases/20150621145122/Packages/Framework/TYPO3.Flow/Scripts/flow.php on
> line 52
>
> Does one of you guys have an idea how I can set the context? Or is only
> Development, Testing and Production possible?
>
> Regards,
> David
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow




-- 
Venlig hilsen Aske

Webudvikler, team lead
MOC A/S
4692 3435 / 4333 2200
moc.net