Pantalaimon: naming conventions
Slavi wrote:
naming conventions:
- the variable for controlling the
pantalaimon.username
setting in the Draupnir role should not be calledmatrix_bot_draupnir_bot_username
, butmatrix_bot_draupnir_pantalaimon_username
. It's the same for the password field. This will also make validation tasks (tasks/validate_config.yml
) clearer. As it is now, I was wondering "Why are these variables only required when Pantalaimon is enabled?". With the correct naming, it's obvious they are part of the samepantalaimon
section of the configuration -
homeserverUrl
(in the Draupnir role) should ideally be controlled via amatrix_bot_draupnir_homeserver_url
variable. Currently, the variable is calledmatrix_bot_draupnir_matrix_csapi_url
. - similarly, for
rawHomeserverUrl
(in the Draupnir role) we should have a newmatrix_bot_draupnir_raw_homeserver_url
variable. Indefaults/main.yml
, it can be defined in terms ofmatrix_homeserver_url
-
matrix_bot_draupnir_use_pantalaimon
should similarly be namedmatrix_bot_draupnir_pantalaimon_use
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information