Skip to content
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

Closed
Den4ik opened this issue Feb 14, 2020 · 5 comments
Closed

[M1] Mutagen configuration for Magento 1 #97

Den4ik opened this issue Feb 14, 2020 · 5 comments
Labels
enhancement New feature or request env-magento1
Milestone

Comments

@Den4ik
Copy link

Den4ik commented Feb 14, 2020

Currently just m2 mutagen configuration available.
Make sense to add configuration for other environment types.

@Den4ik Den4ik changed the title Mutagen configuration for other envirements Mutagen configuration for other enviroments Feb 14, 2020
@Den4ik Den4ik changed the title Mutagen configuration for other enviroments Mutagen configuration for other environments Feb 14, 2020
@davidalger davidalger added the enhancement New feature or request label Feb 19, 2020
@davidalger davidalger added this to the Warden 0.3.0 milestone Feb 19, 2020
@davidalger davidalger removed this from the Warden 0.3.0 milestone Mar 6, 2020
@davidalger
Copy link
Collaborator

@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 local type where the user defines everything, just need to know the use-case, and for specific applications (like Shopware for example) what directories should be excluded from the sync (./var on M2 and Shopware is excluded due to being used for logs and cache files that would make the sync endlessly churn) and/or mounted via a delegated mount (pub/media on M2 is an example, or public/media on Shopware)

@Den4ik
Copy link
Author

Den4ik commented Jul 7, 2020

Hi @davidalger Big thanks for your work.
Only M1 required for me. I added it at my fork. Other types that I use at my projects currently available in warden

@davidalger
Copy link
Collaborator

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:

  • media mounted via delegated mount (and excluded from Mutagen sync)
  • var excluded from Mutagen sync

What does the yml file your using for the sync on M1 look like currently?

@davidalger davidalger changed the title Mutagen configuration for other environments [M1] Mutagen configuration for Magento 1 Jul 7, 2020
@davidalger davidalger added this to the Warden 0.7.0 milestone Jul 7, 2020
@Den4ik
Copy link
Author

Den4ik commented Jul 8, 2020

---
sync:
  defaults:
    mode: two-way-resolved
    watch:
      pollingInterval: 10
    ignore:
      vcs: true
      paths:
        # System files
        - ".DS_Store"
        - "._*"

        # Vim files
        - "*~"
        - "*.sw[a-p]"

        # IDE files
        - "/.idea"

        # Magento files
        - "/media"
        - "/var/**"

    permissions:
      defaultFileMode: "0644"
      defaultDirectoryMode: "0755"

davidalger added a commit that referenced this issue Jul 10, 2020
@davidalger
Copy link
Collaborator

davidalger commented Jul 10, 2020

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request env-magento1
Projects
None yet
Development

No branches or pull requests

2 participants