An Ansible playbook and roles to manage Debian cloud VMs running the Prez Stack.
The Prez Stack consists of the following:
- Apache Jena Fuseki (database)
- Prez (backend web API)
- Prez UI (web server serving static web assets for the Prez UI)
- Nginx (web server - ingress proxy to the stack)
The different components of the Prez Stack run inside containers managed by Podman. The containers themselves are not managed directly with Podman but rather are managed through systemctl. Example, to restart the Fuseki container, run sudo systemctl restart container-fuseki
. However, manual actions such as these shouldn't be required and instead, they should be actioned through a role within the prez.yml
playbook.
Fuseki, Prez and Prez UI all run inside their own containers and they are accessed through an NGINX server running on the target machine.
This playbook assumes a cloud VM with SSH access has been set up. If you are using AWS, it would be an EC2 instance.
Ensure a DNS record has been set to point to the IP of the VM and update the domain name information (see dev_ and prod_ sections) in the hosts
file and the group_vars/dev-webservers.yml
and group_vars/prod-webservers.yml
. This value is used to target the VM machine and also to register an SSL certificate with Let's Encrypt.
Ansible version 2.14 and Python 3.9 - 3.11 is required.
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt
The Ansible hosts
file with a section named dev_webservers
and prod_webservers
manages the target machines these plays apply to.
Note: the following scripts reference the dev env by using dev-, use prod- to run against the prod env.
The files dev-vault.yml
& prod-vault.yml
is encrypted using Ansible Vault. To view or edit the file, run the following.
Note: obtain the password from the system system administrator and create a file ./ansiblepass
before proceeding.
To edit the vault file, run the following.
ansible-vault edit group_vars/dev-vault.yml --vault-password-file ./ansiblepass
These are the variables in the vault.
# Remote server's user, e.g., ec2-user, ubuntu
remote_server_user:
# The Fuseki basic auth credentials
fuseki_user:
fuseki_password:
# The Google Maps API key used by Prez UI
google_maps_api_key:
Run the roles in sequence for a fresh installation. The plays target the hosts with the remote_server_user
defined in group_vars/dev-vault.yml.
Note: modify the letsencrypt variables in group_vars/dev-webservers.yml as required.
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t nginx.install
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t podman.install
Note: modify the container image variable in group_vars/dev-webservers.yml as required.
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t prez-ui.install
Note: modify the Fuseki variables in group_vars/dev-webservers.yml as required.
Fuseki's exposure to the public internet via nginx is controlled by the nginx_expose_fuseki
variable. When the nginx_expose_fuseki
value is changed, run the nginx.install
role to apply to the target hosts.
Fuseki's basic authentication details such as username and password can be changed by editing group_vars/dev-vault.yml
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t fuseki.install
Note: This step is not done for GSWA Prez.
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t fuseki.load-initial-data
Note: modify the Prez variables in group_vars/dev-webservers.yml as required.
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t prez.install
Note: modify the swapfile variables in group_vars/dev-webservers.yml as required.
ansible-playbook -i hosts --vault-password-file ./ansiblepass dev-prez.yml -t swapfile.enable