Applications

Shopware PaaS Native supports multiple applications within a project, such as environments for production, staging, or temporary feature testing.

Each application has its own compute resources, infrastructure, and deployment configuration, so you can tailor each environment to its specific needs.

For instance, you might allocate smaller, hibernating compute instances for staging, while reserving larger, always-on resources for production.

Creating an Application

Deploy a new application to a project:

sw-paas application create

Build and Deployments

To trigger a new build for the application via CLI, use the following command:

sw-paas application build start

This command initiates the build process, packaging your application and preparing it for deployment. While the build is running, you can monitor its progress and view real-time output by following the logs:

sw-paas application build logs

Plugin Management

Plugin management is done via Composer because the platform runs in a high-availability and clustered environment.

In such setups, local changes aren't feasible, as all instances must remain identical and stateless. This ensures consistency across all deployments.

Using Privately Hosted Packages

To pull privately hosted Composer packages, you need to provide authentication credentials. Create a COMPOSER_AUTH secret using the CLI:

sw-paas vault create

Follow the prompts to enter your Composer authentication JSON as a buildenv. This secret will be used during builds to access private repositories.

Executing Commands

Shopware PaaS Native provides two primary ways to run commands in your application environments via CLI: exec and command.

exec Command

The exec command allows you to execute commands in a remote terminal session for your applications. This is useful for running commands directly on your application's environment, such as debugging, maintenance, or running one-off commands interactively.

sw-paas exec --new

This opens an interactive shell session inside your application's container.

command Command

The command command lets you create and manage commands that are executed in dedicated containers. This is particularly useful for CI/CD environments, asynchronous command execution, automated processes, or situations where you don't need to wait for command completion.

Unlike exec, which provides an interactive shell, command runs your specified command in a new, isolated container and does not require you to wait for its completion.

The default execution directory is /var/www/html and the container has a time-to-live (TTL) of 1 hour, so your command must complete within that timeframe.

sw-paas command create

For a complete list of available commands, refer to the Shopware console commands documentation.

Domain Management

Shopware Domain

When you deploy an application for the first time, it automatically receives a complimentary shopware.shop domain. This allows you to access and test your application right away, even before setting up a custom domain.

The assigned domain is generated based on your application's name and unique identifier.

Custom Domain

This feature is under development.