Deployment Notes

There are any number of ways to deploy Errbit, but official support is limited to Heroku.

See specific notes on deployment via:

• Heroku
• Dokku
• Docker
• Kubernetes (experimental)

HTTPS

Errbit can be deployed with HTTPS in a couple different ways.

Nginx or Apache can be used as a reverse-proxy to Errbit’s Puma. In this scenario, Nginx or Apache is configured to serve using HTTPS. The user sends an HTTPS request to Nginx or Apache. Nginx or Apache decrypts the request and passes it on to Errbit using plain HTTP.

Alternatively, Errbit’s Puma can be configured to serve HTTPS directly. Instead of starting Errbit with the command:

bundle exec puma -C config/puma.rb

start it with:

bundle exec puma -b "ssl://0.0.0.0:443?key=server.key&cert=server.crt" -C config/puma.rb

Where server.key is a path to the TLS private key and server.crt is the path to the TLS certificate.

Health Checks

Errbit exposes the default Rails health check at /up, which returns 200 if the app boots with no exceptions, otherwise 500. You can use this endpoint for load balancer or container orchestration health checks.