Skip to main content
Version: Next

Good to know

Sync existing data​

After syncing data from local from /var/ and /public/var, ensure you are running rebuilding your classes:

./bin/console pimcore:deployment:classes-rebuild --create-classes

Logs​

By default configuration, logs are streamed to stderr Platform.sh stores those logs within /var/log/ directory. You can find more details about how to access them here.

Running commands​

You should run your commands using prod env variable --env=prod, especially when you are using interactive shell.

bin/console pimcore:bundle:list --json --no-debug --env=prod

Symfony cache dir​

By default configuration, Symfony cache dir is set to /app/localCache. If you would like to change that consider changing the corresponding mount in the applications.yaml.

Mounting definition files​

The way of working with class definitions is not specific to PaaS, it's a general thing to consider depending on the way how you want to work with class definitions no matter where you run your Pimcore instance.

While in some cases it is useful to have class definitions stored in Git under /var, we do not recommend that. They should really only be in /var if it is possible to change them in the UI (and therefore are not in Git). As soon as they are getting deployed by a pipeline, you should put them manually into the /config folder after creating/modifying them, also them to Git and maintain it there. This ensures a clear separation for immutable deployments and volumes and also avoids confusion for developers.

Following docs are explaining in details Pimcore class definitions and environment specific configurations.

As with Pimcore configurations also Pimcore class definitions are saved as PHP configuration files and therefore can be added to version control systems and be deployed to different deployment stages. The PHP configuration files and PHP classes will be written to the var/classes directory by default. To disallow modification and turn a class to be read-only, you can create a copy at config/pimcore/classes. It all depends on your project specific needs.

Keeping your PaaS bundle up-to-date​

After updating your PaaS bundle to a newer version you also need to update the files that PaaS bundle provides. Command ./vendor/bin/pimcore-paas-install-config accepts flag --force-overwrite or -f. Use this flag with caution, as it will replace your existing files with the new versions from the PaaS bundle. Merging your exiting changes to the latest changes from PaaS bundle is a manual process.