added data logic variables (upcoming, but not even on dev yet)
parent
fb5da26f57
commit
5dfb595bba
@ -184,3 +184,31 @@ Example value: `192.168.0.50` or use docker container names if applicable.
|
||||
Port of the endpoint for the database.
|
||||
|
||||
Example value: `5432`
|
||||
|
||||
## Data Logic
|
||||
|
||||
These variables dictate important logic in the data side of the PYRSS application.
|
||||
|
||||
#### `MAX_SUBSCRIPTIONS_PER_SERVER`
|
||||
|
||||
**Optional / Default `15`**
|
||||
|
||||
The maximum amount of subscriptions that can be created against any given server. This is not a database constraint, but rather is checked in the validation of API requests, meaning it can be bypassed with administrator access.
|
||||
|
||||
Example value: `10`
|
||||
|
||||
#### `MAX_FILTERS_PER_SERVER`
|
||||
|
||||
**Optional / Default `15`**
|
||||
|
||||
The maximum amount of content filters that can be created against any given server. This is not a database constraint, but rather is checked in the validation of API requests, meaning it can be bypassed with administrator access.
|
||||
|
||||
Example value: `10`
|
||||
|
||||
#### `MAX_MESSAGE_STYLES_PER_SERVER`
|
||||
|
||||
**Optional / Default `15`**
|
||||
|
||||
The maximum amount of message styles that can be created against any given server. This is not a database constraint, but rather is checked in the validation of API requests, meaning it can be bypassed with administrator access.
|
||||
|
||||
Example value: `10`
|
||||
|
Loading…
x
Reference in New Issue
Block a user