diff --git a/deployment.html b/deployment.html index d750ad13..8ee16abc 100644 --- a/deployment.html +++ b/deployment.html @@ -107,21 +107,21 @@
EXODUS_GW_
(example: EXODUS_GW_CALL_CONTEXT_HEADER
).
Name of the header from which to extract call context (for authentication and authorization).
Permitted metadata field names for s3 uploads and their regex for validation. E.g., “exodus-migration-md5”: “^[0-9a-f]{32}$”
A set of user or service accounts which are only authorized to publish to a particular set of path(s) in a given CDN environment and the regex(es) describing the paths to which the user or service account is authorized to publish. The user or @@ -135,49 +135,49 @@
Logging configuration in dictConfig schema.
Path to an exodus-gw.ini config file with additional settings.
db service user name
db service user password
db service host
db service port
Connection string for database. If set, overrides the db_service_*
settings.
If set to True, drop all DB tables during startup.
This setting is intended for use during development.
If db_migration_mode
is upgrade
, this setting can be used to override
the target revision when migrating the DB.
The maximum number of attempts to recreate a DB session within a request.
Number of publish items to load from the service DB at one time.
Maximum number of items to write to the DynamoDB table at one time.
Maximum write attempts to the DynamoDB table.
Maximum number of worker threads used in the DynamoDB batch writes.
Maximum number of items the queue can hold at one time.
Maximum amount of time (in seconds) to wait for queue items. Defaults to 10 minutes.
Maximum amount of time (in hours) between updates to a pending publish before it will be considered abandoned. Defaults to one day.
Maximum amount of time (in hours) to retain historical data for publishes and tasks. Publishes and tasks in a terminal state will be erased after this time has passed. Defaults to two weeks.
@@ -272,55 +272,55 @@Maximum amount of time (in days) to retain data on published paths for the purpose of cache flushing.
Maximum amount of time (in hours) a task should remain viable. Defaults to two hours.
Maximum amount of time (in milliseconds) actors may run. Defaults to 30 minutes.
Maximum amount of time (in milliseconds) actors may use while backing off retries. Defaults to five (5) minutes.
List of file names that should be saved for last when publishing.
Filename for indexes automatically generated during publish.
Can be set to an empty string to disable generation of indexes.
Background processing of autoindexes will be disabled for paths matching any of these values.
Time (in minutes) config is expected to live in components that consume it.
Determines the delay for deployment task completion to allow for existing caches to expire and the newly deployed config to take effect.
@@ -328,13 +328,13 @@The path to a file used to verify healthiness of a worker. Intended to be used by OCP
Background worker keepalive timeout, in seconds. If a worker fails to update its status within this time period, it is assumed dead.
This setting affects how quickly the system can recover from issues such as a worker @@ -343,13 +343,13 @@
How often, in seconds, should background workers update their status.
cron-style schedule for cleanup task.
exodus-gw will run a cleanup task approximately according to this schedule, removing old data from the system.
@@ -357,7 +357,7 @@How often, in minutes, exodus-gw should check if a scheduled task is ready to run.
Note that the cron rules applied to each scheduled task are only as accurate as this
interval allows, i.e. each rule may be triggered up to scheduler_interval
minutes late.
Delay, in minutes, after exodus-gw workers start up before any scheduled tasks should run.
Whether ‘commit’ tasks should automatically flush CDN cache for affected URLs.
Only takes effect for environments where cache flush credentials/settings @@ -381,26 +381,26 @@
Whether listing paths in the config should be flushed while deploying the config.
Time (in seconds) cookies generated by cdn-redirect
remain valid.
Time (in seconds) signed URLs remain valid.
Maximum permitted value for expire_days
option on
cdn-access
endpoint.
Clients obtaining signed cookies for CDN using cdn-access
will be
@@ -409,7 +409,7 @@
Number of S3 clients to cache