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

[FEATURE] Include the surge caching plugin by default. #121

Merged
merged 1 commit into from
Dec 21, 2021
Merged

Conversation

jenkoian
Copy link
Contributor

Comment on lines +73 to +75
Surge won't work on VIP environments as it needs the ability to write to the file system. [VIP has its own page caching anyhow](https://docs.wpvip.com/technical-references/caching/page-cache/).

`composer remove wpackagist-plugin/surge`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there anything that can be done to detect the VIP environment and switch this off in those circumstances?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could do this automatically in the vip-install, although it may still be useful to have installed locally. I think it'd likely be part of our deployment script to remove as part of that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which (at the moment at least) I think is outside of the scope of this repository.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's reasonable.

@jenkoian jenkoian merged commit bae602d into main Dec 21, 2021
@jenkoian jenkoian deleted the surge branch December 21, 2021 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants