This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Removed outdated info about installing Fastly #5025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added info about shared Fastly service account used for Magento Commerce Cloud projects - Move info about domain delegation when you already have the Cloud domain and subdomain associated to an existing Fastly account
- Moved info about Fastly service account to intro - Moved domain delegation instructions to intro topic since domain delegation request must be completed before Cloud projects can be added to the service account
- On Cloud Staging and Production environments, the Fastly module is installed automatically - Removed info about installing through Integration branch
hguthrie
suggested changes
Jul 25, 2019
meker12
commented
Jul 25, 2019
meker12
commented
Jul 25, 2019
meker12
commented
Jul 25, 2019
Co-Authored-By: hguthrie <[email protected]>
- Remove content that suggests that you can configure multiple backends from the Magento Admin - Explain that the default Fastly VCL code provides default backend settings for review and update - Add note about integrating additional backends using Fastly Edge modules.
- Verify default Fastly config before customizing settings or enabling advanced features - Update the configuration checklist in topic overview to remove Fastly Image optimization
hguthrie
approved these changes
Jul 26, 2019
| {:#info .bs-callout .bs-callout-info} | ||
| This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp) (also referred to as a _naked_ domain). You must use a DNS | ||
| provider that supports forwarding DNS queries to use an apex domain. | ||
| You need make the following changes to the DNS configuration for your site: |
There was a problem hiding this comment.
Suggested change
| You need make the following changes to the DNS configuration for your site: | |
| You need to make the following changes to the DNS configuration for your site: |
- Fix broken links - Editorial clean up
- Fixed broken link - Cleaned up upgrade topic
meker12
added
Internal Dev
Co-Authored-By: hguthrie <[email protected]>
meker12
commented
Jul 26, 2019
| {:#info .bs-callout .bs-callout-info} | ||
| This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp) (also referred to as a _naked_ domain). You must use a DNS | ||
| provider that supports forwarding DNS queries to use an apex domain. | ||
| To enable Fastly caching on your Staging and Production sites, you need make the following changes to the DNS configuration for your site: |
There was a problem hiding this comment.
Suggested change
| To enable Fastly caching on your Staging and Production sites, you need make the following changes to the DNS configuration for your site: | |
| To enable Fastly caching on your Staging and Production sites, you need to make the following changes to the DNS configuration for your site: |
meker12
commented
Jul 26, 2019
- Fixed broken links - Cleaned up Verify or Debug Fastly services topic
|
running tests |
|
running tests |
|
running tests |
|
Hi @meker12, thank you for your contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
On Cloud Staging and Production environments, the Fastly module is installed automatically. Cloud Guide still says customer must install module on Integration branch.
Updates
Affected DevDocs pages
https://devdocs.magento.com/guides/v2.3/cloud/cdn/configure-fastly.html
https://devdocs.magento.com/guides/v2.3/cloud/cdn/cloud-fastly.html
https://devdocs.magento.com/guides/v2.3/cloud/cdn/trouble-fastly.html
whatsnew
Updated the Fastly Set up instructions to remove the requirement to install the Fastly CDN module for Magento 2 in Magento Commerce Cloud environments. The latest version of the Fastly module is installed by default in Pro Staging and Production environments and in the Starter Production (
master) environment.