...
How code changes trigger the pipeline?
any of code change
How to package the artifact and version it, and what’s the versioning strategy?
separate devops package and the business package to two artifact with the same version number.
the versioning format:
$(echo $(date +'v%Y.%m.%d%H%M'))
How to deploy the specific specify versioned artifact to the specific specify env?
the operator would select a draft release from github releases list, and swith it to a formal release.
the switch event will trigger the deployement of production with a the specific specify version.
How to execute sql migration script or other script of laravel?
sql migration will be run as a ansible task we’d written on
laravelroles.if there’s other script we would like to run on the deployment, we could add it into the end of devops/roles/laravel/tasks/main.yml
How to add configurations to deployment?
Ansible is a configuration system also. The configuration have many levels in Ansible.
What’s the minimal we have to know is that:
where the service will be deployed to?
go to subfolder `devops/env_vars`, you will see the different env folder like stag and prod.
the hosts.yaml file in the env folder contains all host address of servers. You can change it if your server address is change. But you have to commit it to github to trigger the deployement.
where the secret vars are placed?
we define the secret vars on Github repo
we use it as a ansible-play command line var in github actions script.
...
| Code Block | ||
|---|---|---|
| ||
.github
└── workflows
├── compile-to-stage.yml --> compile larasite, package it as a draft release
then deploy the package to stag env by ansible.
├── loki-deployment.yml --> deploy loki server to prod env by triggered
of the specificspecify folder changes.
└── prod-deployment.yml --> deploy larasite to prod env by triggerd
of switching draft release to release
├── README.md
├── ...<other source code>
devops
├── Vagrantfile --> for testing locally
├── common_vars --> common vars for ansible playbook
│ ├── global.yaml --> off
│ ├── loki-docker-compose.yaml
│ └── nginx-vhosts.yaml
├── env_vars
│ ├── prod --> all of prod env configuration in this folder
│ ├── group_vars
│ └── loki.hosts.yaml --> specific loki host
│ └── stag --> all of stag env configuration in this folder
├── group_vars
└── hosts.yaml --> specific larasite host
├── playbook-larasite.yml --> deploy larasite
├── playbook-loki.yml --> deploy loki a kind of log server
├── roles --> each subfolder of it is that meanings a kind of deployment for a component
│ ├── ansible-role-docker
│ ├── ansible-role-loki
│ ├── ansible-role-nginx
│ ├── ansible-role-php
│ ├── ansible-role-php-versions
│ ├── ansible-role-pip
│ ├── ansible-role-promtail
│ └── laravel --> the main logic of deployment for larasite
├── scripts --> store a few script helper
│ └── install-ansible.sh
└── test
└── docker-compose.yaml --> for tesing locally |
...