PaaS: Installation command is outdated after change from PHP script to bash

[mromeike]

Report type

Outdated content

Affected page URL or Markdown path

https://github.com/shopware/docs/blob/main/products/paas/shopware-paas/cli-setup.md

Problem or request

The installation instructions no longer work, because the script is no longer executable for | php, but | bash instead.

Suggested improvement

Update the installation command and possible other unrecorded changes.

Shopware version or version range

no specific version

Context or environment

PaaS project (via Upsun)

Evidence and supporting details

Output from running the setup command currently documented on the page:

> curl -sfS https://cli.shopware.com/installer | php
# Installer for the Shopware PaaS CLI.
#
...

The command simply outputs the whole bash script instead of installing. The change was apparently introduced last week or over the weekend and has caused issues in one of our PaaS projects during deployments (2026-07-20).

Reproduction or discovery steps

curl -sfS https://cli.shopware.com/installer | php

Repository routing confirmation

• This issue is about documentation content or documentation behavior, not a Shopware product or platform bug.

[mromeike]

Just noticed older shopware PaaS CLI versions fail to download https://cli.shopware.com/manifest.json with 404. Not sure if it's related. Does not seem to break anything with those versions, though.

[mromeike]

For lack of a better place to provide this information:

BC was added to the installer, as I saw, but it did not restore the previous functionality:

: <<'PHP'
PHP Fatal error:  Uncaught Error: Undefined constant "STDERR" in Standard input code:17
Stack trace:
#0 {main}
  thrown in Standard input code on line 17

Fatal error: Uncaught Error: Undefined constant "STDERR" in Standard input code:17
Stack trace:
#0 {main}
  thrown in Standard input code on line 17

Not sure why this makes a difference, as both are SAPI cli...

> echo "<?php var_dump(defined('STDERR'));" | php
bool(false)
> php -r "var_dump(STDERR);"
resource(3) of type (stream)

---

In addition, while it's pretty specific, for our Upsun/PaaS hosting, the installation remains broken regardless.

This is caused by the $HOME used by the new installer script to create config_home, being set to a different path during build and runtime. The wrong path is written to $HOME/.local/bin/shopware and fails to call the actual CLI tool, as paths change.

I used the following command to work around the limitation.

            # Install Shopware PaaS CLI
            echo "Using HOME=${HOME} for Shopware PaaS CLI installer..."
            curl -fsSL https://cli.shopware.com/installer | bash

            # Patch the invalid path in the script
            sed -i 's#/app/#$HOME/#' "$HOME/.local/bin/shopware"

[Isengo1989]

Report type

Outdated content

Affected page URL or Markdown path

https://github.com/shopware/docs/blob/main/products/paas/shopware-paas/cli-setup.md

Problem or request

The installation instructions no longer work, because the script is no longer executable for | php, but | bash instead.

Suggested improvement

Update the installation command and possible other unrecorded changes.

Shopware version or version range

no specific version

Context or environment

PaaS project (via Upsun)

Evidence and supporting details

Output from running the setup command currently documented on the page:

> curl -sfS https://cli.shopware.com/installer | php
# Installer for the Shopware PaaS CLI.
#
...

The command simply outputs the whole bash script instead of installing. The change was apparently introduced last week or over the weekend and has caused issues in one of our PaaS projects during deployments (2026-07-20).

Reproduction or discovery steps

curl -sfS https://cli.shopware.com/installer | php

Repository routing confirmation

• This issue is about documentation content or documentation behavior, not a Shopware product or platform bug.

Can you state the OS you used this on? For me, this worked fine.

Patrick Derks (@TrayserCassa) maybe you could take a look here.

[TrayserCassa]

Micha Hobert (@Isengo1989) No this is upsun PaaS, this doesn't belong to the shopware-paas team.
FYI: axasanya