Skip to content

Production Deployment

For production deployment, there are a few things to modified to make sure your deployment is ready for production usage.

Override Docker Compose configuration

You can use docker-compose.override.yml file to override different aspects of your deployment instead of editing docker-compose.yml directly in order to avoid conflict with upstream code.

Where to store persistent files

Default setup

By default, persistent files are stored by writting files to disk on the host system using the Docker's internal volume management.

Be warned

The downside is that files may be hard to locate for tools and applications that run directly on the host system.

Production setup

In production environment create a data directory on the host system and mount this to a directory visible from inside the container.

Recommended for production

This places the persistent files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files.

To achieve this, put the following in the docker-compose.override.yml file inside ShellHub project dir:

version: '3.7'
      - /usr/local/mongo/data:/data/db

Make sure /usr/local/mongo/data directory exists on the host.

Enable SSL

When running in production you should ensure that you enable SSL

This is commonly achieved by running Nginx with your certificates on your Docker host, service or load balancers in-front of the running container.

Don't forget to set SHELLHUB_PROXY environment when putting a Layer 4 load balancer with proxy protocol in-front of ShellHub.