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

Makes dev-env closer to vip go #284

Merged
merged 5 commits into from Sep 30, 2022
Merged

Makes dev-env closer to vip go #284

merged 5 commits into from Sep 30, 2022

Conversation

pschoffer
Copy link
Contributor

@pschoffer pschoffer commented Sep 15, 2022

This change sets some constants and config to behave more closely to VIP go platform.

  • Also some HTTPS manipulation needed to support eg. define( 'FORCE_SSL_ADMIN', true );

Solves #267

sjinks
sjinks previously approved these changes Sep 19, 2022
@WPprodigy
Copy link
Contributor

WPCOM_IS_VIP_ENV being true could be misleading 😬

@pschoffer
Copy link
Contributor Author

WPCOM_IS_VIP_ENV being true could be misleading grimacing

In what way @WPprodigy ? It does seem to control a lot of places and significantly changes WP behaviour (e.g. no plugin installs)

It feels to me that in order to get closer to real platform setup we want this to be true, or?

@WPprodigy
Copy link
Contributor

This constant is being used in codebases to determine if a site is on a live VIP env or if its elsewhere - like a local environment. I don't think it's very clear or true to say a local environment === a vip environment.

@rinatkhaziev rinatkhaziev dismissed sjinks’s stale review September 20, 2022 18:04

see Caleb's feedback

@pschoffer
Copy link
Contributor Author

Gread points. I removed the setting of WPCOM_IS_VIP_ENV from this PR.

@pschoffer pschoffer merged commit 02b4a6b into master Sep 30, 2022
@pschoffer pschoffer deleted the update/vip-dev-env-parity branch September 30, 2022 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants