Skip to content

Latest commit

 

History

History
38 lines (25 loc) · 1.02 KB

README.sentry.md

File metadata and controls

38 lines (25 loc) · 1.02 KB
Raw

Sentry-specific Changes

Running Locally with Docker-Compose

For all docker-compose operations please use our compose.sh wrapper.

To run the demo locally, configure Sentry DSN values for every service in the demo in .env.sentry file, and then run it as follows:

# Copy the example file
cp .env.sentry.example .env.sentry

# Update Sentry DSN values in `.env.sentry`
# ...

# Start docker-compose
./compose.sh up

You can add an optional docker-compose.override.yml file if you want to override various values for local development or testing.

Compose configuration will be read (and overridden) in the following order:

  1. docker-compose.yml
  2. docker-compose.sentry.yml
  3. docker-compose.override.yml

So the values in docker-compose.override.yml will "win" over the corresponding values in the other files.

Deploying the Demo

When you are happy with the local changes, you can deploy your changes to our live demo instances.

See ./deploy/README.md for more details.