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

[Karsten Dambekalns]

Hi.

Currently we need one index.php per context. This sucks equally well for 
CLI and web access.

The idea of using an environment variable came up in the past, and I 
tried that today.


CLI - done and working

For CLI usage, simply set FLOW3_CONTEXT to the name of the context, e.g.
  FLOW3_CONTEXT=Development php index.php ...
or
  FLOW3_CONTEXT=Development ./flow3 ...


Apache - not really a problem

The line
  SetEnvIf Request_URI "^/index_dev\.php" FLOW3_CONTEXT=Development
sets the variable, it is passed through as REDIRECT_FLOW3_CONTEXT in the 
following URL rewriting. Cool.

Combine this with a slightly changed Router class (adjusting the check 
for the script name being present in route()) and it works.

Question: Is there a more elegant way of embedding the context in the URL?
Task: Keep the context in URL generated by FLOW3.

Arbitrary contexts - a problem?

Looking at the SetEnvIf line it becomes clear that this will not work 
for index_testing.php or index_funny.php. Adding another SetEnvIf is not 
too hard, but should it be needed?

One solution could be to ucfirst() the context from the environment 
variable, then it would work if combined with a rewrite rule like
  ^(?:index(?:_([a-z]+))?.php)?(.*)$ /index.php?/$2 [E=FLOW3_CONTEXT:$1]

The drawback would be that one would have to write index_development.php

Is support for arbitrary contexts something we should have? Is it worth 
the trouble?


Regards,
Karsten