@@ -33,29 +33,24 @@ We recommend running courier with no changes to the configuration and no paramet
33
33
environment variables to configure it. You can use ` % courier --help ` to see a list of the
34
34
environment variables and parameters and for more details on each option.
35
35
36
- ### RapidPro
37
-
38
- For use with RapidPro/TextIt, you will want to configure these settings:
39
-
40
36
* ` COURIER_DOMAIN ` : The root domain which courier is exposed as (ex ` textit.in ` )
41
37
* ` COURIER_SPOOL_DIR ` : A local path where courier can spool files if the database is down, should be writable. (ex: ` /home/courier/spool ` )
42
38
* ` COURIER_DB ` : Details parameters used to connect to the Postgres RapidPro database (ex:
` postgres://textit:[email protected] /5432/textit ` )
43
39
* ` COURIER_REDIS ` : Details parameters to use to connect to Redis RapidPro database (ex: ` redis://redis-internal.courier.io:6379/13 ` )
44
40
* ` COURIER_AUTH_TOKEN ` : authentication token to require for requests from Mailroom
45
-
46
- For writing of message attachments, Courier needs access to an S3 bucket, you can configure access to your bucket via:
47
41
48
- * ` COURIER_S3_REGION ` : The region for your S3 bucket (ex: ` ew-west-1 ` )
49
- * ` COURIER_S3_ATTACHMENTS_BUCKET ` : The name of your S3 bucket (ex: ` rp-attachments ` )
50
- * ` COURIER_S3_ATTACHMENTS_PREFIX ` : The prefix to use for filenames of attachments added to your bucket (ex: ` attachments ` )
51
- * ` COURIER_AWS_ACCESS_KEY_ID ` : The AWS access key id used to authenticate to AWS
52
- * ` COURIER_AWS_SECRET_ACCESS_KEY ` The AWS secret access key used to authenticate to AWS
42
+ ### AWS services:
43
+
44
+ * ` COURIER_AWS_ACCESS_KEY_ID ` : AWS access key id used to authenticate to AWS
45
+ * ` COURIER_AWS_SECRET_ACCESS_KEY ` AWS secret access key used to authenticate to AWS
46
+ * ` COURIER_AWS_REGION ` : AWS region (ex: ` eu-west-1 ` )
47
+ * ` COURIER_S3_ATTACHMENTS_BUCKET ` : name of your S3 bucket (ex: ` rp-attachments ` )
53
48
54
- Recommended settings for error and performance monitoring :
49
+ ### Logging and error reporting :
55
50
56
- * ` COURIER_LIBRATO_USERNAME ` : The username to use for logging of events to Librato
57
- * ` COURIER_LIBRATO_TOKEN ` : The token to use for logging of events to Librato
58
- * ` COURIER_SENTRY_DSN ` : The DSN to use when logging errors to Sentry
51
+ * ` COURIER_DEPLOYMENT_ID ` : used for metrics reporting
52
+ * ` COURIER_SENTRY_DSN ` : DSN to use when logging errors to Sentry
53
+ * ` COURIER_LOG_LEVEL ` : logging level to use (default is ` warn ` )
59
54
60
55
## Development
61
56
0 commit comments