Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Feedback on page: /guides/v2.2/cloud/deploy/reduce-downtime.html #4252

Closed
kotasthanesp opened this issue Apr 15, 2019 · 2 comments
Closed

Feedback on page: /guides/v2.2/cloud/deploy/reduce-downtime.html #4252

kotasthanesp opened this issue Apr 15, 2019 · 2 comments
Assignees
Labels
2.x Internal Dev Differentiates work between community and Magento staff

Comments

@kotasthanesp
Copy link

General issue

Confusion about what constitutes 'ideal state wizard'

Description:

"Configure static content deployment
If static content deployment fails in the deploy phase, your site gets stuck in maintenance mode. When a failure occurs during the build phase, the process avoids downtime because it never begins the deploy phase. Generating static content during the build phase with minified HTML, also known as the ideal state, is the optimal configuration for zero-downtime deployments and prevents downtime if a failure occurs.

You can validate your project configuration by running the ideal state wizard."
In this para, it suggests that ideal state can be achieved by only confirming two settings: SCD on build and HTML minification. But in the actual docs link about ideal state wizard, there is a 3rd setting about configuring post-deploy hook.

We should be consistent about whether post-deploy hook is a necessary pre-req to achieving 0-downtime deploy or not.

Possible solutions:

Maybe we can say that #2 and #3 together constitute ideal-state. Not just the two settings mentioned in #2.

Additional information:

@hguthrie
Copy link
Contributor

hguthrie commented May 6, 2019

Another good point. I moved the statement about the ideal state wizard to the end of the list and added an emphasis. Once you're done with the list, you can run ideal state wizard to confirm configuration settings...in case more checks are added to ideal state in the future.

@hguthrie hguthrie added 2.x Internal Dev Differentiates work between community and Magento staff labels May 6, 2019
hguthrie added a commit that referenced this issue May 6, 2019
@dobooth
Copy link
Contributor

dobooth commented May 7, 2019

Fixed with merge.

@dobooth dobooth closed this as completed May 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2.x Internal Dev Differentiates work between community and Magento staff
Projects
None yet
Development

No branches or pull requests

3 participants