[wp-trac] [WordPress Trac] #51064: Consider adding "local" as environment on WP_ENVIRONMENT_TYPE
WordPress Trac
noreply at wordpress.org
Fri Aug 21 23:22:19 UTC 2020
#51064: Consider adding "local" as environment on WP_ENVIRONMENT_TYPE
----------------------------+---------------------
Reporter: claytoncollie | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: 5.5.1
Component: Bootstrap/Load | Version: 5.5
Severity: normal | Resolution:
Keywords: 2nd-opinion | Focuses:
----------------------------+---------------------
Comment (by khag7):
#50992 seems to be going the opposite direction from this ticket: they
state there that the list of environment "types" should be limited to
"development" "staging" and "production".
A noteworthy snippet from a recent comment there:
>One of the challenges we've run into with the environment type label is
that it's quite narrow and conflates different things:
> * Where is this application running? (e.g. local environment or remote
environment)
> * What is the application’s purpose (e.g. production site; non-
production site; staging site; etc.)
Maybe the solution here should be to come up with a way to define "where"
the application is running. Then we can allow #50992 to restrict the
environment type (i.e. purpose) to the three "development" "staging" and
"production".
If local vs remote is defined in some different way (yet another
constant?) then you could use that constant to differentiate between
development(remote) and development(local).
If this is a bad idea (introducing a new constant to define local vs
remote) then we're stuck in a position of deciding which ticket we
implement and which we don't. Seems like #50992 is on track to win,
meaning this ticket doesn't lead to any implementation.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/51064#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list