Skip to content

include environment in default outputPath #57

@kellyselden

Description

@kellyselden

We are testing concurrent deployments using threads. We are doing this locally, but I figured it might make sense as the default:

outputPath: `tmp/deploy-dist-${environment}`

I started making a PR, but since the environment is dynamic and the defaults are defined as static, I couldn't figure out how to get it to work, especially with the EMBER_CLI_DEPLOY_REUSE_BUILD section. Also, how would you detect if someone already customised the outputPath before appending the environment?

Metadata

Metadata

Assignees

No one assigned

    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