Using a multi-environment configuration
In any modern deployment workflow, we have four environments: local, dev, test, and production. Each of these environments may have different configurations and tunings. Your production environment will probably have to face tons of users and a heavy load in a clustered system, while your local environment will just need to fight with the amount of RAM. What we see is that each environment has different needs, and consequently, needs different configurations. The approach that we want to follow is to keep all the data in a single code base and keep all the settings in the same place. If you are thinking that you'll need to manage a lot of files and complicated logic to switch them, you are wrong.
Fortunately, Pimcore is based on Symfony and extends its very powerful configuration system. Pimcore manages dev, test, and prod environments natively (while others can be added with an additional configuration). To switch the environment, you...