Since Composer-install is the preferred “future” way to use TYPO3 I try to figure out how to have the Server-setup for that.
Now the different TYPO3 system- src versions are located in /usr/share/ and available for the hosted sites.
Sites have symlinks towards the TYPO3 base to make it work. Updating or using different versions side by side is very easy. Also saving space, since not every site has its own TYPO3 system-files installed. Only having local files when needed (extensions, site-packags etc.)>
Will this work the same way, when using composer setup? How to deal with that?
I followed the instructions from the manual for migrating to a composer system. Version control — TYPO3 Upgrade Guide main documentation
I still do not get the whole picture here Would be help-full if I could see an example of a similar set-up. Or a howto/ instruction, info, etc. on how to set things up for such a approach.
Sites are now public available in /var/www/domain/www while having symlinks to /usr/share/typo3-src
And with the folders for local use - fileadmin - typo3conf - ext. etc.
But with the new or required setup for composer the folder structure has changed? Does this mean the set-tup I have now will not work any more? And do I need to run composer per site? As in the ddev example?