Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define TODO list for deploy command #35

Open
tdgroot opened this issue Apr 16, 2018 · 2 comments
Open

Define TODO list for deploy command #35

tdgroot opened this issue Apr 16, 2018 · 2 comments
Assignees

Comments

@tdgroot
Copy link
Collaborator

tdgroot commented Apr 16, 2018

I'm sure @Robin31 and @Wesdesignz can provide a list of steps that need to be added to the deploy command.

@WesleyVestjens
Copy link

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.

@WesleyVestjens
Copy link

This issue is blocked until issue #37 is resolved.

@WesleyVestjens WesleyVestjens self-assigned this Apr 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants