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

Make the Project Platform/Host Agnostic #23

Open
mogmarsh opened this issue Jun 27, 2023 · 0 comments
Open

Make the Project Platform/Host Agnostic #23

mogmarsh opened this issue Jun 27, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mogmarsh
Copy link
Contributor

Description

When we moved a client site from Pantheon to VIP, we had a repo set up for a few weeks that could deploy to both hosts. If it deployed to Pantheon, there was a minimal mu-plugins directory that would load everything in client-mu-plugins and the plugin loader was set up to conditionally load some of the plugins that VIP includes in mu-plugins. If it deployed to VIP, that mu-plugins directory was ignored, and things worked as expected.
We could also provide some wrapper functions for things that the hosts handle differently such as caching related functions.

Use Case

With some of our clients bouncing between hosts or making last minute decisions on hosting due to budget and bidding wars, it made me wonder if we could somehow build a setup that would work on both VIP and Pantheon, and we could just make it our stock setup. This would make things more consistent for developers across projects as well.

@mogmarsh mogmarsh added the enhancement New feature or request label Jun 27, 2023
@srtfisher srtfisher linked a pull request Nov 15, 2023 that will close this issue
@srtfisher srtfisher removed a link to a pull request Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant