You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding to the list of helpful Booleans (IsDebug, IsSuper, IsAccuratyIp, IsUrlSpecial(), etc.), we need a reasonably reliable way to determine if the project is running in production vs. staging. Production basically means its either released and live, and in front of the public (client for Intranet). Staging would mean we are working on it and/or this version of the project is a clone or something; running locally or from a non-production URL.
Method name: IsStaging() // TBD?
For convenience, IsProduction() => !IsStaging() ??
To solve this we return true on the follow conditions (WIP):
is the current site running on an Accuraty-based subdomain? List below.
is the current site HttpContext.Current.Request.IsLocal
more WIP
Exception Handling: What if a site/project actually is staging, but doesn't match a list item above?
How would we handle this custom? What site settings could set that is easy to discover and implement (and detect) so that a project could be true for IsStaging()? This could or should also work to temporarily flip a production site to staging if/when needed (seems like a likely need). For this latter case, maybe we implement this with a Duration? E.g. flip to staging for 4 hours.
Accuraty staging domains for project deployments:
ACCURATY.US
ACCURATY.WS
ACCURATY.???
The text was updated successfully, but these errors were encountered:
Adding to the list of helpful Booleans (IsDebug, IsSuper, IsAccuratyIp, IsUrlSpecial(), etc.), we need a reasonably reliable way to determine if the project is running in production vs. staging. Production basically means its either released and live, and in front of the public (client for Intranet). Staging would mean we are working on it and/or this version of the project is a clone or something; running locally or from a non-production URL.
Method name: IsStaging() // TBD?
For convenience, IsProduction() => !IsStaging() ??
To solve this we return true on the follow conditions (WIP):
HttpContext.Current.Request.IsLocal
Exception Handling: What if a site/project actually is staging, but doesn't match a list item above?
How would we handle this custom? What site settings could set that is easy to discover and implement (and detect) so that a project could be true for IsStaging()? This could or should also work to temporarily flip a production site to staging if/when needed (seems like a likely need). For this latter case, maybe we implement this with a Duration? E.g. flip to staging for 4 hours.
Accuraty staging domains for project deployments:
The text was updated successfully, but these errors were encountered: