-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[M1] Mutagen configuration for Magento 1 #97
Comments
@Den4ik Just circling around to this. The 0.6.0 release will be including a new Shopware environment type with Mutagen configuration. The current images and setup will now support the flexibility needed to do this for more than just the Magento 2 environment type. What types would you like to see Mutagen sync added for? I've seen a request for it on Magento 1 but that was scratched and deemed non-necessary. Open to adding this on other environment types, perhaps even just making it a standard for any type on macOS other than the |
Hi @davidalger Big thanks for your work. |
Got it. Sounds like it may be useful to add a config for M1 then, and then call this one closed. This will leave Warden operating Mutagen syncs on macOS for M1, M2 and Sh6. For M1, what I'll probably do (unless someone suggests differently) is similar to M2 and have:
What does the yml file your using for the sync on M1 look like currently? |
|
@Den4ik This is implemented in the develop mainline and will be released in the upcoming 0.7.0 release. Seems to work well in my testing on an M1 project I just on-boarded for a new client we're about to migrate to M2 over here. Let me know what you think. |
Currently just m2 mutagen configuration available.
Make sense to add configuration for other environment types.
The text was updated successfully, but these errors were encountered: