This project leverages GitHub Actions for streamlined automation. While most variables are securely stored as GitHub Secrets for heightened security, there's an exception.
One crucial variable, LINUX_HOST, is intentionally exposed as a GitHub Secret. Despite its sensitive nature, this approach is adopted to simplify customization for developers cloning this project. The decision stems from the project's non-commercial orientation.
dev directory is using for dev environment to test the workflows such as act because rsa private key do not work with local environment (work only in github secret environment somehow) so in local we need to use base64 private key instead
The rationale behind this choice is to empower developers with a seamless experience. By making LINUX_HOST a secret, you can effortlessly clone this project and tailor the variable directly in your GitHub repository settings. This eliminates the need for code modifications for basic configuration adjustments.
every workflow was set to on workflow_dispatch means you have to navigate to Action Tabs in Github website, in this repository and press Run to run each workflow.
This is done because not every service need to re-deploy when push to some branch
** Further improve by testing when push to branch
- DOCKERHUB_USERNAME
- DOCKERHUB_TOKEN
- LINUX_HOST
- LINUX_USERNAME
- LINUX_PRIVATE_KEY_BASE64
- ELASTIC_PASSWORD
- ELASTIC_USERNAME
- AUTH_DB_USER
- AUTH_DB_PASSWORD
- JWT_KEY
- SENDER_PASSWORD
- SUPER_ADMIN_PASSWORD
- SUPER_ADMIN_EMAIL
- ADMIN_PASSWORD
- ADMIN_EMAIL
- USER_PASSWORD
- USER_EMAIL
- DATA_MNGMNT_DB_USER
- DATA_MNGMNT_DB_PASSWORD
- LINUX_PRIVATE_KEY
- SUPER_ADMIN_USERNAME
- RABBITMQ_USERNAME
- RABBITMQ_PASSWORD
- GRAFANA_USERNAME
- GRAFANA_PASSWORD