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

Improve build and deploy env definitions #8843

Merged
merged 3 commits into from
Mar 30, 2021
Merged

Improve build and deploy env definitions #8843

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fbf9704
Improve build and deploy env definitions
Mar 29, 2021
f28005c
Improve build and deploy env definitions
Mar 29, 2021
7ce1279
Changes as per review
Mar 30, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Improve build and deploy env definitions
  • Loading branch information
Barny committed Mar 29, 2021
commit f28005cd5bd330bea95f312cc1f1d32a050c832b
7 changes: 3 additions & 4 deletions src/cloud/live/sens-data-over.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,13 +51,13 @@ You can also set sensitive values using the Magento CLI command: `bin/magento co

Depending on the size of your store, you may have a large amount of static content files to deploy. Normally, static content deploys during the deploy phase when Magento is in Maintenance mode. The most optimal configuration is to generate static content during the build phase. See [Choosing a deploy strategy][scd].

If you have enabled Configuration Management after dumping the configurations, you should move the SCD_* variables (in `.magento.env.yaml`) from the deploy to the build stage to properly enable static content generation in the build phase.
If you have enabled Configuration Management after dumping the configurations, you should move the SCD_* variables (in `.magento.env.yaml`) from the deploy to the build stage to properly enable static content generation in the build phase.

### Example

Before Configuration Management:

```
```yaml
deploy:
CRON_CONSUMERS_RUNNER:
cron_run: true
Expand All @@ -70,7 +70,7 @@ Before Configuration Management:

After enabling Configuration Management, move the SCD_* variables to the build stage:

```
```yaml
deploy:
CRON_CONSUMERS_RUNNER:
cron_run: true
Expand All @@ -82,7 +82,6 @@ After enabling Configuration Management, move the SCD_* variables to the build s
...
```


{:.bs-callout-info}
Before deploying static files, the build and deploy phases compress static content using GZIP. Compressing static files reduces server loads and increases site performance. Refer to [Magento build options]({{ site.baseurl }}/cloud/env/variables-build.html) to learn about customizing or disabling file compression.

Expand Down
4 changes: 2 additions & 2 deletions src/cloud/project/magento-env-yaml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ If you have enabled Configuration Management after dumping the configurations, y

Before Configuration Management:

```
```yaml
deploy:
CRON_CONSUMERS_RUNNER:
cron_run: true
Expand All @@ -42,7 +42,7 @@ Before Configuration Management:

After enabling Configuration Management, move the SCD_* variables to the build stage:

```
```yaml
deploy:
CRON_CONSUMERS_RUNNER:
cron_run: true
Expand Down