Closed DavidBruchmann closed 5 years ago
I thought it would be possible to set the paths as environment variables
That is true.
Did I misunderstand the sense of that code?
No.
but I never succeeded
It would be helpful to know what exactly you tried in order to be able to help.
I thought it would be possible to set the paths as environment variables
Although I wouldn't recommend doing so. It shouldn't be necessary and it is likely this option is removed in future versions of the installer.
Thank's for the fast answer. I tried it in windows with git-bash as well as with cmd, so perhaps I've to try it in Linux ...,
reason is that directories can change and even on one server you've to install first in a dev-directory and afterwards in a live-directory whereas the latter one can't be changed on some servers.
reason is that directories can change and even on one server you've to install first in a dev-directory and afterwards in a live-directory whereas the latter one can't be changed on some servers.
What I am trying to say is, that whatever use case you have, it is likely that it needs a different implementation once the possibility to change directories via environment variables is removed.
Therefore I'd recommend to not rely on an implementation that won't work in the future, but look for a different way to implement your use case.
But I guess this can be closed then? Correct?
If you need further support you can ask in compose channel on TYPO3 Slack
Ok, thanks. There exists another composer-extension for those things but I thought this would be smarter.
Seeing the file CmsComposerInstallers/res/php/autoload-include.tmpl.php I thought it would be possible to set the paths as environment variables and those would be taken then, but I never succeeded. Did I misunderstand the sense of that code?