TYPO3.Flow

I agree. Currently the paths are configured inside the batch script itself which is not the optimal solution.
I think, a nice way to do this would be to extract the configuration lines to a new file (e.g. flow3config.default) and copy the contents to a file flow3config (if it does not yet exist) which will be included by the script. flow3config should then be added to svn ignore list of course.

In the Windows batch version (that I'm currently working on) that could look something like

...
IF NOT EXIST flow3config.bat COPY flow3config.default.bat config.bat
CALL flow3config.bat
...

Anyone knows the Unix pendant for this?

Karsten Dambekalns wrote:

Applied in changeset r3903.

Sorry, but i do not see how this resolves the issue?

Why not check if a config file is available and source it if available?

#!/bin/bash

PHP="/usr/bin/env php";
# Other variables with their default values

# So the configfile can override all default variables.
CONFIGFILE="$(dirname $0)/Configuration/flow3.sh";
if [ -f "$CONFIGFILE" ]; then
    source $CONFIGFILE
fi

Bastian Waidelich wrote:

Anyone knows the Unix pendant for this?

source "PATH_TO_FILE" 

#or

. "PATH_TO_FILE" 

Thomas Fritz wrote:

Karsten Dambekalns wrote:

Applied in changeset r3903.

Sorry, but i do not see how this resolves the issue?

Why not check if a config file is available and source it if available?

Why a configuration file? On most systems I'd expect to by the system PHP binary the "right" one anyway. If not, just call

PHP=/usr/local/freaky-php/bin/php ./flow3 ...

Honestly, a config file seems like overkill to me.

Karsten Dambekalns wrote:

Thomas Fritz wrote:

Karsten Dambekalns wrote:

Applied in changeset r3903.

Sorry, but i do not see how this resolves the issue?

Why not check if a config file is available and source it if available?

Why a configuration file? On most systems I'd expect to by the system PHP binary the "right" one anyway.

Thats not the case on shared hosted systems. And the path is not mandatory anyway.

If not, just call
[...] or export the variable if you use it more often.

That looks and feels very clumsy. What if there is a /usr/bin/php available and the right one would be a different one. When more than one developer uses the flow3 script everyone has to know which one to use and can not call flow3 directly. And if one calls it directly this could trigger an error then.

Honestly, a config file seems like overkill to me.

Why is an optional config file an overkill? FLOW3 is in every way convenient and configurable but not in this case?

A config file is easier to create in an automated build script as exporting ENV Variables with path. And it is more flexible if one would need more configuration values in its shell scripts.

Environment variables are IMHO the most common way to solve those issues. I would always prefer that way to having to create a config file. So, if anyone comes up with a good reason and a readymade solution to this, fine. I won't work on this issues more, as I consider it fixed. Sorry ;)

And, by the way, FLOW3 tries not to be configurable wherever possible.