764a040a90
People who wish to rely on SRV records can prevent the `/.well-known/matrix/server` file from being generated (and thus, served.. which causes trouble).
48 lines
1.6 KiB
YAML
48 lines
1.6 KiB
YAML
# The bare hostname which represents your identity.
|
|
# This is something like "example.com".
|
|
# Note: this playbook does not touch the server referenced here.
|
|
hostname_identity: "{{ host_specific_hostname_identity|lower }}"
|
|
|
|
# This is where your data lives and what we set up here.
|
|
# This and the Riot hostname (see below) are expected to be on the same server.
|
|
hostname_matrix: "matrix.{{ hostname_identity }}"
|
|
|
|
# This is where you access the web UI from and what we set up here.
|
|
# This and the Matrix hostname (see above) are expected to be on the same server.
|
|
hostname_riot: "riot.{{ hostname_identity }}"
|
|
|
|
|
|
matrix_user_username: "matrix"
|
|
matrix_user_uid: 991
|
|
matrix_user_gid: 991
|
|
|
|
matrix_base_data_path: "/matrix"
|
|
matrix_base_data_path_mode: "750"
|
|
|
|
matrix_static_files_base_path: "{{ matrix_base_data_path }}/static-files"
|
|
|
|
matrix_homeserver_url: "https://{{ hostname_matrix }}"
|
|
|
|
matrix_identity_server_url: ~
|
|
|
|
# The Docker network that all services would be put into
|
|
matrix_docker_network: "matrix"
|
|
|
|
# Controls whether a `/.well-known/matrix/server` file is generated and used at all.
|
|
#
|
|
# If you wish to rely on DNS SRV records only, you can disable this.
|
|
# That implies that you'll be handling Matrix Federation API traffic (tcp/8448)
|
|
# using certificates for the base domain (`hostname_identity`) and not for the
|
|
# matrix domain (`hostname_matrix`).
|
|
matrix_well_known_matrix_server_enabled: true
|
|
|
|
# Variables to Control which parts of our roles run.
|
|
run_setup: true
|
|
run_import_postgres: true
|
|
run_upgrade_postgres: true
|
|
run_start: true
|
|
run_register_user: true
|
|
run_import_sqlite_db: true
|
|
run_import_media_store: true
|
|
run_self_check: true
|