[Flow] Changing Contexts in Neo
Adrian Föder
adrian at foeder.de
Mon Mar 24 09:31:28 CET 2014
Hi Greg,
I have installed Flow on a Synology, too, and in Production it's working
*acceptably* (but, beware, without Neos, which brings a couple of
additional load).
Anyway, 15 seconds sounds like Dev context, are you sure you're running
in Production?
Best,
Adrian
Am 23.03.2014 08:49, schrieb Greg Greg:
> Quote: Olivier Dobberkau (oli4) wrote on Wed, 10 October 2012 11:28
> ----------------------------------------------------
>> Am 09.10.12 21:57, schrieb Martin:
>> <font color="8c8c8c">> try</font>
>> <font color="8c8c8c">> </font>
>> <font color="8c8c8c">> SetEnv FLOW3_CONTEXT=Production</font>
>> <font color="8c8c8c">> </font>
>> <font color="8c8c8c">> That was working for me in a FLOW3
>> Applikation</font>
>>
>> OK. After this:
>>
>> FLOW_CONTEXT=Production ./flow flow:cache:flush
>> FLOW_CONTEXT=Production ./flow flow:cache:warmup
>>
>> we have a nice working DEMO Site.
>>
>> Thanks,
>>
>> Olivier
> ----------------------------------------------------
>
> Thanx.
> That s working better with this lines.
> Like you, I have performance problem.
> But I have installed Neos on a Synology NAS (DS212+). Perhaps it s the
> server capacity and performance which is the culprit.... I don't know.
> But, now, I haven't internal error 500, but it s slow : 15 second to
> navigate in frontend between link on the top of the demo site.
>
>
>
More information about the Flow
mailing list