You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation says that AdditionalConfiguration.php will only be modified if file does not exists or is managed by DDEV.
For TYPO3, DDEV settings are written to AdditionalConfiguration.php. If AdditionalConfiguration.php exists and is not managed by DDEV, it will not be modified.
This is not true for ddev config when TYPO3 is has been set up
Hint in ddev config about this behavior:
TYPO3 does not seem to have been set up yet, missing LocalConfiguration.php ([...]/public/typo3conf/AdditionalConfiguration.php)
I can recreate this and agree that this isn't the expected behavior, although it does seem unlikely to have an unmanaged AdditionalConfiguration.php and no LocalConfiguration.php. I'll put this into our next sprint.
Explanation why i need this: I'm recreating the boilerplate for our TYPO3 projects using ddev. There we have dotenv configurations within the AdditionalConfiguration.php but TYPO3 is not installed yet (no LocalConfiguration.php) before calling ddev config.
The documentation says that AdditionalConfiguration.php will only be modified if file does not exists or is managed by DDEV.
This is not true for
ddev config
when TYPO3 is has been set upHint in
ddev config
about this behavior:To Reproduce
Steps to reproduce the behavior:
composer create-project typo3/cms-base-distribution my-typo3-site ^8
cd my-typo3-site
echo "<?php" > public/typo3conf/AdditionalConfiguration.php
ddev config
Expected behavior
AdditionalConfiguration.php should not be modified.
Version and configuration information:
The text was updated successfully, but these errors were encountered: