Changeset View
Changeset View
Standalone View
Standalone View
docker/README.md
Show First 20 Lines • Show All 654 Lines • ▼ Show 20 Lines | (swh)$ docker-compose \ | ||||
-f docker-compose.storage-replica.override.yml \ | -f docker-compose.storage-replica.override.yml \ | ||||
run \ | run \ | ||||
swh-journal-backfiller \ | swh-journal-backfiller \ | ||||
snapshot \ | snapshot \ | ||||
--start-object 000000 \ | --start-object 000000 \ | ||||
--end-object 000001 \ | --end-object 000001 \ | ||||
--dry-run | --dry-run | ||||
``` | ``` | ||||
## Using Sentry | |||||
All entrypoints to SWH code (CLI, gunicorn, celery, ...) are, or should be, | |||||
intrumented using Sentry. By default this is disabled, but if you run your | |||||
own Sentry instance, you can use it. | |||||
To do so, you must get a DSN from your Sentry instance, and set it as the | |||||
value of `SWH_SENTRY_DSN` in the file `env/common_python.env`. | |||||
You may also set it per-service in the `environment` section of each services | |||||
in `docker-compose.override.yml`. |