Pontoon is designed to be deployed on Heroku. To deploy an instance of Pontoon on Heroku, you must first create an app on your Heroku dashboard. The steps below assume you’ve already created an app and have installed the Heroku Toolbelt.
For quick and easy deployment without leaving your web browser, click this button:
Pontoon uses several buildpacks in a specific order. They are (in order):
- heroku-buildpack-apt for installing Subversion.
- heroku-buildpack-ssh for setting up the SSH keys necessary for committing to version control.
- The official
heroku/nodejsbuildpack for installing Node.js programs for pre-processing frontend assets.
- The official
heroku/pythonbuildpack as our primary buildpack.
You can set these buildpacks on your app with the following toolbelt commands:
# Note that we use add and --index 1 to append to the top of the list. heroku buildpacks:set heroku/python heroku buildpacks:add --index 1 heroku/nodejs heroku buildpacks:add --index 1 https://github.com/Osmose/heroku-buildpack-ssh.git#v0.1 heroku buildpacks:add --index 1 https://github.com/mozilla/heroku-buildpack-apt.git#v0.1
The following is a list of environment variables you’ll want to set on the app you create:
- Optional. Email address for the
- Optional. Name for the
- Controls whether asynchronous tasks (mainly used during sync) are sent to
Celery or executed immediately and synchronously. Set this to
- Maximum number of tasks a Celery worker process can execute before it’s replaced with a new one. Defaults to 20 tasks.
./manage.py collectstaticduring the build. Should be set to
Heroku’s Python buildpack has a bug that causes issues when running node binaries during the compile step of the buildpack. To get around this, we run the command in our post-compile step (see
bin/post_compile) when the issue doesn’t occur.
DEBUGmode for the site. Should be set to False in production.
- Signifies whether this is a development server or not. Should be False in production. Adds some additional django apps that can be helpful during day to day development.
- Optional. URL to the page displayed to your users when the application encounters a system error. See Heroku Reference for more information.
- Optional. URL to the page displayed to your users when the application is placed in the maintenance state. See Heroku Reference for more information.
- Optional. API key for accessing the New Relic REST API. Used to mark deploys on New Relic.
- Optional. Name to give to this app on New Relic. Required if you’re using New Relic.
- Optional. A list of project manager email addresses to send project requests to
- Required. Secret key used for sessions, cryptographic signing, etc.
- Controls the base URL for the site, including the protocol and port.
http://localhost:8000, should always be set in production.
Contents of the
~/.ssh/configfile used when Pontoon connects to VCS servers via SSH. Used for disabling strict key checking and setting the default user for SSH. For example:
StrictHostKeyChecking=no Host hg.mozilla.org User firstname.lastname@example.org Host svn.mozilla.org User email@example.com
- SSH private key to use for authentication when Pontoon connects to VCS servers via SSH.
- Optional. Hostname to prepend to static resources paths. Useful for serving
static files from a CDN. Example:
- Path to prepend to
LD_LIBRARY_PATHwhen running SVN. This is necessary on Heroku because the Python buildpack alters the path in a way that breaks the built-in SVN command. Set this to
Some environment variables, such as the SSH-related ones, may contain
newlines. The easiest way to set these is using the
tool to pass the contents of an existing file to them:
heroku config:set SSH_KEY="`cat /path/to/key_rsa`"
- Timezone for the dynos that will run the app. Pontoon operates in UTC, so set
Pontoon executes asynchronous jobs using Celery. These jobs are handled by
worker process type. You’ll need to manually provision workers based on
how many projects you plan to support and how complex they are. At a minimum,
you’ll want to provision at least one
heroku ps:scale worker=1
Pontoon is designed to run with the following add-ons enabled:
- Database: Heroku Postgres
- Performance Monitoring: New Relic APM
- Log Management: Papertrail
- Error Tracking: Raygun.io
- Email: Sendgrid
- Scheduled Jobs: Heroku Scheduler
- Cache: Memcachier
- RabbitMQ: CloudAMQP
It’s possible to run with the free tiers of all of these add-ons, but it is recommended that, at a minimum, you run the “Standard 0” tier of Postgres.
Pontoon uses `django-bmemcached`_, which expects the following environment variables from the cache add-on:
- Semi-colon separated list of memcache server addresses.
- Username to use for authentication.
- Password to use for authentication.
By default, the environment variables added by Memcachier are prefixed
MEMCACHIER instead of
MEMCACHE. You can “attach” the
configuration variables with the correct prefix using the
heroku addons:attach resource_name --as MEMCACHE
resource_name with the name of the resource provided by the cache
addon you wish to use, such as
memcachier:100. Use the
heroku addons command to see a list of resource names that are available.
Similar to the cache add-ons, Pontoon expects environment variables from the RabbitMQ add-on:
- URL for connecting to the RabbitMQ server. This should be in the format for Celery’s BROKER_URL setting.
Again, you must attach the resource for RabbitMQ as
RABBITMQ. See the
note in the Cache Add-ons section for details.
Pontoon requires a single scheduled job that runs the following command:
It’s recommended to run this job once an hour. It commits any string changes in the database to the remote VCS servers associated with each project, and pulls down the latest changes to keep the database in sync.
Sync Log Retention¶
You may also optionally run the
clear_old_sync_logs management command on a
schedule to remove sync logs from the database that are over 90 days old:
After deploying Pontoon for the first time, you must run the database migrations. This can be done via the toolbelt:
heroku run ./manage.py migrate
Creating an Admin User¶
After deploying the site, you can create a superuser account using the
createsuperuser management command:
heroku run ./manage.py createsuperuser --noinput --user=admin --firstname.lastname@example.org
If you’ve already logged into the site with the email that you want to use, you’ll have to use the Django shell to mark your user account as an admin:
heroku run ./manage.py shell # Connection and Python info... >>> from django.contrib.auth.models import User >>> user = User.objects.get(email@example.com') >>> user.is_staff = True >>> user.is_superuser = True >>> user.save() >>> exit()
SSH_CONFIGenvironment variables requires a rebuild of the site, as these settings are only used at build time. Simply changing them will not actually update the site until the next build.
The Heroku Repo plugin includes a rebuild command that is handy for triggering builds without making code changes.