This pull request primarily focuses on improving the deployment workflow and environment setup for the application. The changes include adding a new environment variable, restructuring the GitHub Actions workflows, and updating the Sentry initialization in the bot setup.
Environment setup:
.env.example: Added a new environment variable DEPLOY_ENVIRONMENT. This is used to determine the deployment environment (e.g., staging, production) for the application.
README.md: Updated the documentation to include the new DEPLOY_ENVIRONMENT variable.
src/app/bot.py: Modified the Sentry initialization to include the DEPLOY_ENVIRONMENT variable. This allows Sentry to know the environment in which the error occurred.
GitHub Actions workflows:
.github/workflows/conoha.yml: Made significant changes to the workflow structure. The workflow now includes steps for setting up the environment (conoha-setup), checking the code (conoha-check), building the application (conoha-build), and deploying the application (conoha). The environment setup step determines the deployment environment based on the branch (master for production, staging for staging). The deployment step now uses the DEPLOY_ENVIRONMENT variable for environment-specific configurations. [1][2][3][4][5]
.github/workflows/docker-ci.yml: Similar changes were made to this workflow, including adding an environment setup step (docker-ci-setup) and using the DEPLOY_ENVIRONMENT variable in the Docker image building step. [1][2]
This pull request primarily focuses on improving the deployment workflow and environment setup for the application. The changes include adding a new environment variable, restructuring the GitHub Actions workflows, and updating the Sentry initialization in the bot setup.
Environment setup:
.env.example: Added a new environment variableDEPLOY_ENVIRONMENT. This is used to determine the deployment environment (e.g., staging, production) for the application.README.md: Updated the documentation to include the newDEPLOY_ENVIRONMENTvariable.src/app/bot.py: Modified the Sentry initialization to include theDEPLOY_ENVIRONMENTvariable. This allows Sentry to know the environment in which the error occurred.GitHub Actions workflows:
.github/workflows/conoha.yml: Made significant changes to the workflow structure. The workflow now includes steps for setting up the environment (conoha-setup), checking the code (conoha-check), building the application (conoha-build), and deploying the application (conoha). The environment setup step determines the deployment environment based on the branch (master for production, staging for staging). The deployment step now uses theDEPLOY_ENVIRONMENTvariable for environment-specific configurations. [1] [2] [3] [4] [5].github/workflows/docker-ci.yml: Similar changes were made to this workflow, including adding an environment setup step (docker-ci-setup) and using theDEPLOY_ENVIRONMENTvariable in the Docker image building step. [1] [2]