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
The 2 main steps that we intended to create for the build command was DI compilation (this step was done) and static content deploy.
To finish the static content deploy command, we need to solve the following issue: a config.php with stores + enabled modules or a working database is required in order to run the static content deploy command.
I was personally thinking of creating/generating a dummy config.php so we can deploy static content, however, this would not be the most pretty solution. @Robin31 has created a yaml configuration file which can be read. This file contains configuration for the static content deploy.
If we can generate a app/etc/config.local.php from this file while building, we should be able to deploy static content and push the generated content to .init.
Activity
WesleyVestjens commentedon Apr 16, 2018
The 2 main steps that we intended to create for the build command was DI compilation (this step was done) and static content deploy.
To finish the static content deploy command, we need to solve the following issue: a config.php with stores + enabled modules or a working database is required in order to run the static content deploy command.
I was personally thinking of creating/generating a dummy config.php so we can deploy static content, however, this would not be the most pretty solution. @Robin31 has created a yaml configuration file which can be read. This file contains configuration for the static content deploy.
If we can generate a
app/etc/config.local.phpfrom this file while building, we should be able to deploy static content and push the generated content to.init.WesleyVestjens commentedon Apr 17, 2018
This issue is blocked until issue #37 is resolved.