[wp-trac] [WordPress Trac] #33161: Create a standard for defining and identifying site environment

[WordPress Trac]

#33161: Create a standard for defining and identifying site environment
--------------------------------+-----------------------------
 Reporter:  krogsgard           |       Owner:  SergeyBiryukov
     Type:  enhancement         |      Status:  accepted
 Priority:  normal              |   Milestone:  5.5
Component:  Options, Meta APIs  |     Version:  4.2
 Severity:  normal              |  Resolution:
 Keywords:  needs-patch         |     Focuses:
--------------------------------+-----------------------------

Comment (by ev3rywh3re):

 Replying to [comment:17 johnbillion]:
 > The reason I'd like to hear ''specifics'' is because every time I
 encounter this problem, the logic that alters behaviour based on the
 environment happens really early, in `wp-config.php`, meaning a filterable
 function will trigger too late for a lot of per-environment logic.

 I was actually looking to see if there were comments beyond the dev,
 staging, and live usage. For a specific use how about a temp site built on
 a local vm used for quick and dirty host/domain migrations? I’ve done this
 with a hacked site in the past as well for content restoration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33161#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform