| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |
| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |
| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |
| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |
| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |
| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |
| Variable | +Comments | +
|---|---|
timezone |
+ list all available timezones with timedatectl
+ list-timezones Examples +
|
+
ansible_connection |
+ Depends on the Architecture you are
+ adopting, default is lxd Options +
|
+
lxd_network |
+ Here you define a network which your containers will be created into,
+ default is 172.19.2.1/24 |
+
lxd_bridge_interface |
+ The name of the created lxd bridge, default is lxdbr1 |
+
| Variable | +Comments | +
|---|---|
create_db |
+ Whether the database should be created or not Choices: +
|
+
database_host |
+ Host to use as your database server Default= postgres |
+
dhis2_war_file |
+ Source for your dhis2 war file, can either be remote or available
+ locally as file Examples +
|
+
dhis2_version |
+ You can specify just the major version of dhis2 and it will get its
+ latest stable iteration from https://releases.dhis2.org. If your + have both dhis2_war_file and dhis2_version
+ defined, dhis2_war_file wins,
+ Examples
|
+
heap_memory_size |
+ This is tomcat Java Heap Memory Size, Example + heap_memory_size=2G |
+
| Variable | +Comments | +
|---|---|
postgresql_version |
+ Version for PostgreSQL to be installed, in a fresh install, the is default: `16` | +
pg_max_connections |
+ Maximum allowed connections to the database | +
pg_shared_buffers |
+ Shared Buffers for postgresql, recommended 0.25 x Available_RAM for PostgreSQL |
+
pg_work_mem |
+ PostgreSQL work memory, Recommended = (0.25 x Available_RAM)/max_connections |
+
pg_maintenance_work_mem |
+ As much as you can reasonably afford. Helps with index generation during the analytics generation task |
+
pg_effective_cache_size |
+ Approx 80% of (Available RAM - maintenance_work_mem - max_connections*work_mem) |
+
| Variable | +Comments | +
|---|---|
fqdn |
+ This is the domain used to access dhis2 application Strictly required for Letsencrypt to work |
+
email |
+ Strictly required if you are using Letsencrypt | +
proxy |
+ Proxy software of your choice Options +
|
+
SSL_TYPE |
+ This parameter enables to specify whether you'd want to use
+ letsencrypt or your own customssl
+ certificate,Options
|
+
munin_base_path |
+ Base path for accessing munin, e.g:
+ https://domain.example.com/munin_base_path defaults to munin
+ |
+
munin_users |
+ A list of users with their corresponding passwords allowed to login to munin:
+ Example:
+
+
+ Default username and password is admin and district respectively.
+ |
| Variable | +Comments | +
|---|---|
s3_access_key |
+ This is a unique identifier for cloud user or programmatic entity + (like an application) that needs to interact with object storage. | +
s3_secret_key |
+ This is a secret piece of information that is associated with the + Access Key. It is used to digitally sign requests made to object storage + and maybe other services. This Secret Access Key must be kept confidential, + as it's used to authenticate and authorize requests on behalf of the Access + Key. | +
s3_cluster_id |
+ Cluster URL for Object Storage is unique to each data center, + different data-centers have unique cluster IDS, refer to + Linode Object Storage Guide + for Linode. | +
s3_bucket |
+ This is a container or storage resource for storing files in the + context of object storage + |