[FLOW3-general] ./flow3 kickstart argument passing

[Rens Admiraal]

Hi,

Some of the changes are quite recent, and documentation is indeed being
updated. So this will probably be explained in the docs soon. 

If you look at the content of flow3_dev against flow3 you see flow3_dev
is just forcing Development context even if the environment vars are
configured for another context. AFAIK there's no further difference,
but maybe someone reading this can correct me :-)

Greetz,
Rens


On 2011-06-15, Nicolas Forgerit <nicolas.forgerit at gmail.com> wrote:
> Hey!
>
> I think it really is a bit confusing by now since huge parts of the
> stuff are being rewritten and reshaped but as long as i understand,
> they decided to separate the more user-alike-y (flush cache, compile,
> shell, security) stuff from the more developer-alike-y (doctrine,
> create/list/(de-)activate packages, routing)  stuff. Otherwise the
> cli-tool would be bursting at its seems with its whole lot of options.
> I assume that Contexts (as in sense of F3) don't have anything to do
> with that.
> However, as far as i can see the help texts were not adjusted
> correctly, but i'm not sure about that.
>
> But maybe Rens can bring that to light.
>
> Ciao
>   Nico
>
> PS: For myself, i also wasn't familiar with the --package-key option
> and always tried to use the "shortcut"
> "kickstart:kickstart:generatepackage <PkgKey>" up until it peeved me
> and i just copied the Demo-package. :o)
>
>
> On Wed, Jun 15, 2011 at 12:59 PM, Denyerec <denyerec at gmail.com> wrote:
>> Hi Rens,
>> Am I missing something in the whole ./flow3  versus  ./flow3_dev ?
>> Do we use one commandline tool for the dev context, and one for production?
>> So far as I could see (Though admittedly it was rather late last night!) the
>> tutorials only mention running the ./flow3  tool and don't talk about a
>> ./flow3_dev one.
>>
>> Apologies for my confusion!
>> Denyer
>>


-- 

--
Rens Admiraal
Core Developer V5 Team

TYPO3 .... inspiring people to share!
Get involved: typo3.org