[TYPO3-team-core-v5] Getting rid of index_dev.php - please give feedback

[Malte Jansen]

Hi,

Martin Kutschker schrieb:
> Malte Jansen schrieb:
>> Hi,
>>
>> Martin Kutschker schrieb:
>>> Malte Jansen schrieb:
>>>> Hi Karsten,
>>>>
>>>> what about putting the context somewhere in the usersession.
>>> But you don't need always a session. I can imagine a standalone CLI
>>> FLOW3 package that doesn't need user authentication. Yet you may want to
>>> debug it. But OTOH the whole index_dev.php doesn't look like to be very
>>> CLI friendly either.
>> Ok, user-session might not fit.
>> But what about a debug-session (or ContextManager)?
>>
>> Some small scenario:
>> 1. Activate debug-session (you might need some password)
>> 2. Make your command,test,... what ever you want in the context. You see
>>  the errors...
>> 3. Deactivate debugsession or a timeout
>> 4. Make your command,test,... what ever you want in the context. Just
>> see the result of the productive-context.
>>
>> In the CLI you don't have to change the commands for the context, which
>> might be pretty useful, if you use the commandline-history (normally
>> arrow up/down). In most cases, you don't have to change the command for
>> the CLI or the URL for a WebRequest.
> 
> Looks like the use environment solution to me. And that's what I didn't
> like about it. In the shell anyone can set the environment.

You could protect it with some RSA-Key or something simular to the 
my.cnf of MySQL (storing the mysql-password there, instead of in a 
php-script).
So, just some people can change the enviroment via command.

  But if it
> doesn't bother us a CLI switch like --context or --FLOW3-context might
> be also handy sometimes (overruling the environment).
This should only work, if you allow overruling the enviroment, like 
dis-/enabling the Install-Tool in T3 4.x.

Cheers,

Malte