MCLOUD-3180 update the Configuration management topic #7147
Conversation
This file contains 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
fixed broken links due to extensive updates
hguthrie
added
Major Update
shiftedreality
approved these changes
May 12, 2020
meker12
requested changes
May 13, 2020
| @@ -35,7 +35,7 @@ For all Starter environments and Pro Integration environments, pushing your Git | |||
| - [`.magento.env.yaml`]({{ site.baseurl }}/cloud/project/magento-env-yaml.html)—centralizes the management of build and deploy actions across all of your environments, including Pro Staging and Production, using environment variables. | |||
| - [`.magento/routes.yaml`]({{ site.baseurl }}/cloud/project/project-conf-files_routes.html)—defines how Magento processes an incoming URL. | |||
| - [`.magento/services.yaml`]({{ site.baseurl }}/cloud/project/project-conf-files_services.html)—defines the services Magento uses by name and version. For example, this file may include versions of MySQL, PHP extensions, and Elasticsearch. These are referred to as *services*. | |||
| - [`app/etc/config.php`]({{ site.baseurl }}/cloud/live/sens-data-over.html)—defines the [system-specific settings]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-clp-settings) Magento uses to configure your store. Magento auto-generates this file if it does not detect it during the build phase and includes a list of modules and extensions. If the file exists, the build phase continues as normal, compresses static files using `gzip`, and deploys the files. If you follow [Configuration Management]({{ site.baseurl }}/cloud/live/sens-data-over.html) at a later time, the commands update the file without requiring additional steps. | |||
| - [`app/etc/config.php`]({{ site.baseurl }}/cloud/live/sens-data-over.html)—defines the [system-specific settings]({{ site.baseurl }}/cloud/live/sens-data-over.html#configuration-data) Magento uses to configure your store. Magento auto-generates this file if it does not detect it during the build phase and includes a list of modules and extensions. If the file exists, the build phase continues as normal, compresses static files using `gzip`, and deploys the files. If you follow [Configuration Management]({{ site.baseurl }}/cloud/live/sens-data-over.html) at a later time, the commands update the file without requiring additional steps. | |||
There was a problem hiding this comment.
the commands update ... what commands?
There was a problem hiding this comment.
I don't know. This was only a link update.
There was a problem hiding this comment.
This is a description of the config.php file for configuration management, which is what this PR is about.
| 1. Open the `config.local.php` file and copy the contents. | ||
|
|
||
| 1. Paste the contents into the `config.php` file, save, and complete adding it to Git. |
There was a problem hiding this comment.
Suggested change
| 1. Paste the contents into the `config.php` file, save, and complete adding it to Git. | |
| 1. Paste the contents into the `config.php` file, save, and then commit and push the change to the remote environment. |
There was a problem hiding this comment.
Yeah, this is the section that I requested more information for in the MCLOUD ticket. I have no idea what is going on here.
m2-community-project
bot
added
Progress: changes requested
and removed
Progress: approved
labels
|
@meker12 It looks like you merged master into my branch? Why? |
I built a new staging preview for the additional review request in Slack, and I always update branches to master before I build those. Sorry for stepping on your branch. |
Yes, please do not do that in the future. I do not use merge to update a branch, especially while in review. Thanks. |
m2-community-project
bot
added
Progress: review
and removed
Progress: changes requested
labels
meker12
requested changes
May 14, 2020
| @@ -35,7 +35,7 @@ For all Starter environments and Pro Integration environments, pushing your Git | |||
| - [`.magento.env.yaml`]({{ site.baseurl }}/cloud/project/magento-env-yaml.html)—centralizes the management of build and deploy actions across all of your environments, including Pro Staging and Production, using environment variables. | |||
| - [`.magento/routes.yaml`]({{ site.baseurl }}/cloud/project/project-conf-files_routes.html)—defines how Magento processes an incoming URL. | |||
| - [`.magento/services.yaml`]({{ site.baseurl }}/cloud/project/project-conf-files_services.html)—defines the services Magento uses by name and version. For example, this file may include versions of MySQL, PHP extensions, and Elasticsearch. These are referred to as *services*. | |||
| - [`app/etc/config.php`]({{ site.baseurl }}/cloud/live/sens-data-over.html)—defines the [system-specific settings]({{ site.baseurl }}/cloud/live/sens-data-over.html#cloud-clp-settings) Magento uses to configure your store. Magento auto-generates this file if it does not detect it during the build phase and includes a list of modules and extensions. If the file exists, the build phase continues as normal, compresses static files using `gzip`, and deploys the files. If you follow [Configuration Management]({{ site.baseurl }}/cloud/live/sens-data-over.html) at a later time, the commands update the file without requiring additional steps. | |||
| - [`app/etc/config.php`]({{ site.baseurl }}/cloud/live/sens-data-over.html)—defines the [system-specific settings]({{ site.baseurl }}/cloud/live/sens-data-over.html#configuration-data) Magento uses to configure your store. Magento auto-generates this file if it does not detect it during the build phase and includes a list of modules and extensions. If the file exists, the build phase continues as normal, compresses static files using `gzip`, and deploys the files. If you follow [Configuration Management]({{ site.baseurl }}/cloud/live/sens-data-over.html) at a later time, the commands update the file without requiring additional steps. | |||
There was a problem hiding this comment.
This is a description of the config.php file for configuration management, which is what this PR is about.
meker12
approved these changes
May 14, 2020
|
running tests |
|
Hi @hguthrie, thank you for your contribution! |
|
YAY! Merged! Thank you @meker12 for help reviewing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request (PR) provides extensive updates to the Cloud configuration management information.
Affected DevDocs pages
Configuration management for store settings
Remaining tasks
whatsnew
Updated the Cloud guide Configuration management for store settings topic.