Daria Motorina

следует создать ещё одну бд в которой продублировать таблицы и подготовить для них фикстуры

Most Symfony applications read their configuration from environment variables. While developing locally, you'll usually store these in .env and .env.local (for local overrides). On production, you have two options:

Create "real" environment variables. How you set environment variables, depends on your setup: they can be set at the command line, in your Nginx configuration, or via other methods provided by your hosting service.
Or, create a .env.local file just like your local development (see note below)
There is no significant advantage to either of the two options: use whatever is most natural in your hosting environment.

docker-compose.yml
docker/
   \--> bash/
      \--> .bashrc
      \--> .bash_history

php-fpm:
        user: ${HOST_USER}  
        working_dir: /app
        build:
            context: ./docker/php-fpm
            dockerfile: Dockerfile
        volumes:
            - .:/app
            - ./docker/php-fpm/log/:/var/log/
            - ./docker/bash/.bashrc:/home/${HOST_USER_NAME}/.bashrc
            - ./docker/bash:/home/${HOST_USER_NAME}/bash
            - /etc/group:/etc/group:ro
            - /etc/passwd:/etc/passwd:ro
        ports:
            - '9000:9000'
        networks:
            - internal
        ports:
            - '9000:9000'
        networks:
            - internal

export HISTFILE=~/bash/.bash_history
touch $HISTFILE