Trigger.dev Self-Hosting Docker

If you want to run the Trigger.dev platform yourself, instead of using our cloud product, you can use this repository to get started.

Local development

If you want to self-host the Trigger.dev platform, when you're developing your web app locally you'll need to run the Trigger.dev platform locally as well.

Initial setup

1. Clone this repository and navigate to it:

git clone https://github.com/triggerdotdev/docker.git
cd docker

2. Create your .env file:

cp ./.env.example ./.env

3. Populate any missing .env file values. (See the .env.example file for more instructions)

4. The ports in the docker-compose.yml file are set so they are less likely to clash with your local webapp – the platform runs on 3030 and the database is on 5433. If you need to change these ports, you'll need to update the LOGIN_ORIGIN APP_ORIGIN and DATABASE_HOST environment variables.

Starting the Docker containers

1. Run docker-compose to start the Trigger.dev platform:

docker-compose up -d

Stopping the Docker containers

1. Run docker-compose to stop the Trigger.dev platform:

docker-compose stop

Getting started with using Trigger.dev

You should now be able to access the Trigger.dev dashboard at http://localhost:3030.

To create an again, login using "Magic Link" and the email with the sign-in link will be printing to the console output in the running triggerdotdev container.

Our main docs are at docs.trigger.dev.

Note, you'll need to ensure that you set the apiUrl (usually set via the TRIGGER_API_URL environment variable) to point at your local Trigger.dev at http://localhost:3030.

Use the main tag

The ghcr.io/triggerdotdev/trigger.dev:latest image is the latest official release of Trigger.dev. If you'd like to use the very newest changes, change the image to use our main tag in the docker-compose.yml file, like so:

image: ghcr.io/triggerdotdev/trigger.dev:main