Skip to content

Define TODO list for deploy command #35

Open

Description

@tdgroot

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

Activity

  1. WesleyVestjens commented on Apr 16, 2018

    @WesleyVestjens

    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.

  2. WesleyVestjens commented on Apr 17, 2018

    @WesleyVestjens

    This issue is blocked until issue #37 is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions