spt/Website
spt/Website
2
2
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: enhance documentation

Browse Source
This commit is contained in:
SPT-dev 2023-03-02 21:25:09 -05:00
parent e73b316a13
commit a30298e43a
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
.ansible/README.md
View File

@ -1,19 +1,26 @@
# Website Deployment # Website Deployment
The deployment happens on commit and merge on `master` branch and it is handled by [DroneCI](https://drone.sp-tarkov.com/SPT-AKI/Website) and Ansible. The deployment happens on commit and merge on `master` branch and it is handled by [DroneCI](https://drone.sp-tarkov.com/SPT-AKI/Website) and Ansible.
## Deployment flow ## Deployment flow
The deployment pipeline lives in:
- [.drone-docker.yml](../.drone-docker.yml) for the official [DroneCI](https://drone.sp-tarkov.com/SPT-AKI/Website)
- [.drone-kubernetes.yml](../.drone-kubernetes.yml) for anyone testing this on a DroneCI in Kubernetes
On development and feature branches, the deployment flow is: On development and feature branches, the deployment flow is:
- cloning the project - Cloning the project
- replacing values for ansible inventory file using DroneCI secrets - Replacing values for ansible inventory file using DroneCI secrets
- Checking the playbook syntax - Checking the playbook syntax
- Running the playbook in dry-run mode - Running the playbook in dry-run mode
On master, the deployment flow is: On master, the deployment flow is:
- cloning the project - Cloning the project
- replacing values for ansible inventory file using DroneCI secrets - Replacing values for ansible inventory file using DroneCI secrets
- Checking the playbook syntax - Checking the playbook syntax
- Running the playbook in dry-run mode - Running the playbook in dry-run mode
- Executing the playbook - Executing the playbook
## The playbook ## The playbook
It has only one instruction: Go to the directory in the server and `git pull` to update everything. It has only one instruction: Go to the directory in the server and `git pull` to update everything.