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
Latest alpha release, enabled mutagen support in an existing PHP (symfony) based project. Mutagen.yml has been created with the following content:
sync:
defaults:
mode: "two-way-resolved"
ignore:
paths:
# /var/www/html/var does not need to sync in TYPO3
- "var"
- ".ddev"
vcs: true
symlink:
mode: "portable"
While it is true that the sync is not necessary in TYPO3, in my symfony project of type "PHP" var is quite important to be synced, because I keep the sqlite database there.
Run a Diagnostic and Paste Link Here
https://gist.github.com/susannemoog/7a9be8437997b81152084ad6c750b25e
Describe the bug
Latest alpha release, enabled mutagen support in an existing PHP (symfony) based project. Mutagen.yml has been created with the following content:
While it is true that the sync is not necessary in TYPO3, in my symfony project of type "PHP" var is quite important to be synced, because I keep the sqlite database there.
To Reproduce
ddev config:
see also https://github.com/TYPO3GmbH/site-intercept/blob/develop/.ddev/config.yaml (old config, bug occurred after "ddev config --mutagen-enabled && ddev start")
Expected behavior
var is not excluded if it is not a TYPO3 project - or: make it more obvious that the user has to take care of this decision.
Version and configuration information (please complete the following information):
Additional context
I'm not sure this is even considered to be a bug, maybe it's just expected behaviour I didn't expect ;)
The text was updated successfully, but these errors were encountered: