I am working on improving the chapters on console commands and am wondering:
In all places that we mention commands in the docs we HAVE to repeat: if you are in compose mode call like this, if in classic mode, call like that etc.
As the classic mode seems to stick around and be widely used would it maybe be feasible to create a symlink or something like that in the directoy vendor/bin (a vendor folder is created also in classic mode installations)
This would remove a lot of if you are in this mode do that from places where we just tell ppl to delete the cache or whatever.
It might even be sufficient to just not remove bin from packaging:
https://github.com/TYPO3/darth/blob/main/conf/release.yaml#L82
Oliver Hader:
21. Juli um 09:14 Uhr
I think we need to think twice, what the consequences might be, when having https://example.org/vendor/bin/typo3 exposed in the webroot (in case it would be linked).
Besides that, the binary folder does contain a bunch of other files when being installed with composer install --no-dev - e.g.
ls bin
fluid php-parse typo3 yaml-lint
See complete discussion: https://typo3.slack.com/archives/C03AM9R17/p1752996037645639
I am working on improving the chapters on console commands and am wondering:
In all places that we mention commands in the docs we HAVE to repeat: if you are in compose mode call like this, if in classic mode, call like that etc.
As the classic mode seems to stick around and be widely used would it maybe be feasible to create a symlink or something like that in the directoy vendor/bin (a vendor folder is created also in classic mode installations)
This would remove a lot of if you are in this mode do that from places where we just tell ppl to delete the cache or whatever.
It might even be sufficient to just not remove bin from packaging:
https://github.com/TYPO3/darth/blob/main/conf/release.yaml#L82
Oliver Hader:
21. Juli um 09:14 Uhr
I think we need to think twice, what the consequences might be, when having https://example.org/vendor/bin/typo3 exposed in the webroot (in case it would be linked).
Besides that, the binary folder does contain a bunch of other files when being installed with composer install --no-dev - e.g.
ls bin
fluid php-parse typo3 yaml-lint
See complete discussion: https://typo3.slack.com/archives/C03AM9R17/p1752996037645639