Composer mode in PaaS environments

sebastian.wagner

It seems like the environment variable SPRYKER_COMPOSER_MODE dedicates the mode composer uses to install dependencies within PaaS pipelines.

What is the default setting in PaaS when not touching this variable in deploy.*.yml?
Should I use my deploy-files to overwrite this default variable setting?
Can I use the Parameter Store to adjust its value?

fsmeier

Heyhey, got some feedback from our docker-sdk team:

What is the default setting in PaaS when not touching this variable in deploy.*.yml?

SPRYKER_COMPOSER_MODE doesn’t have the default value.

Should I use my deploy-files to overwrite this default variable setting?

Yes, via the deploy file we can adjust the composer configuration, e.g depends on the working environment.

• dev mode

composer:
    mode: ''
    autoload: ''

• prod mode with --no-dev and optimised autoload

composer:
    mode: --no-dev
    autoload: --classmap-authoritative

Can I use the Parameter Store to adjust its value?

No, you can handle the composer configuration via deploy file.

Hope this helps :)

Lauren Kulwicki

@sebastian.wagner just to note, I moved your question over here into the Developer Corner space :)

fsmeier

Heyhey, got some feedback from our docker-sdk team:

What is the default setting in PaaS when not touching this variable in deploy.*.yml?

SPRYKER_COMPOSER_MODE doesn’t have the default value.

Should I use my deploy-files to overwrite this default variable setting?

Yes, via the deploy file we can adjust the composer configuration, e.g depends on the working environment.

• dev mode

composer:
    mode: ''
    autoload: ''

• prod mode with --no-dev and optimised autoload

composer:
    mode: --no-dev
    autoload: --classmap-authoritative

Can I use the Parameter Store to adjust its value?

No, you can handle the composer configuration via deploy file.

Hope this helps :)

sebastian.wagner

So i doulbe checked and an environment with composer.mode: —no-dev didn't contain dev dependencies, thank you.