Your environment can be configured to include one of the following options, which are officially supported by our DevOps team:

Dokku Platform-as-a-Service

  • Heroku-like experience - includes command line interface for managing configuration options, SSL certificates, and more
  • Git based deployment method
  • Supports every major programming language and Web framework via open source "buildpacks"
  • Getting Started Guide

Docker in Swarm Mode

Good for teams already comfortable with native Docker containerization tools.

  • Better parity between development, test, and production environments
  • Start off with a single machine; expand to a cluster over time
  • Ability to leverage public Docker images
  • Optional git deploy functionality
  • Documentation

Direct-to-Virtual Machine Deployments

  • Git based deployment method
  • Application dependencies are installed directly on top of the operating system
  • You are responsible for any post-deploy steps such as asset compresssion, database migrations, and application restarts by providing a custom build script.

Alpha Releases - Contact Us for Details

Do It Yourself

If you'd like go with a DIY approach, we recommend using an orchestration / configuration management framework such as Ansible, Chef, Puppet, or Salt, with the following guidelines:

  • Application and service log files containing PHI should be routed to /data/log.
  • The Docker Engine is configured to save data to /data/docker. You will need to define separate data volumes for services that need to persist data, such as databases. These can be mounted to any location under /data, for example: /data/myapp-or-service/storage.
  • For customers running their own database service, you are responsible for ensuring data and log files containing PHI are stored on the encrypted data volume, as well as patching your database engine for security issues. If you want to avoid these hassles, use our database-as-a-service option.