@@ -54,7 +54,42 @@ current health of your clone with: -
5454
5555 pre-commit run --all-files
5656
57- ## Local execution
57+ ## Installation
58+ The repository contains an ansible playbook that can be used to simplify the
59+ deployment of the application into a pre-existing Kubernetes ** Namespace** but you will
60+ need to customise the playbook by first defining your own variables.
61+
62+ To install the application follow the steps below.
63+
64+ From a poetry shell, install the required dependencies: -
65+
66+ poetry install --with deploy
67+
68+ Move to the ` ansible ` directory and define your variables: -
69+
70+ pushd ansible
71+
72+ > All the _ required_ variables can be found at the top of the standard
73+ `default/main.yaml` file, but you are advised to inspect all the variables to
74+ ensure they are suitable for your installation (variables are defined in
75+ `default/main.yaml` and `vars/main.yaml`).
76+
77+ You can create a ` parameters.yaml ` file and set your variables there.
78+ A ` parameters-template.yaml ` file is provided as an example. This is protected from
79+ accidental commits as it's in the project's ` .gitignore ` file: -
80+
81+ cp parameters-template.yaml parameters.yaml
82+
83+ Then, when you have set your variables, run the playbook: -
84+
85+ ansible-playbook site.yaml -e @parameters.yaml
86+
87+ To remove the application run the playbook again, but set the ` ess_state ` variable
88+ to ` absent ` : -
89+
90+ ansible-playbook site.yaml -e @parameters.yaml -e ess_state=absent
91+
92+ ## Local development
5893You can build and run the service using ` docker compose ` : -
5994
6095 docker compose up --build --detach
0 commit comments