You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Our automated pipeline currently deploys to the staging environment at nest.owasp.dev. As the project evolves, it's time to establish a dedicated production environment for nest.owasp.org, which currently redirects to staging.
Describe the solution you'd like
Enhance CI/CD workflows, Docker configurations, Ansible playbooks, and any other necessary setups to enable automated deployments to the Nest production environment triggered by creating a GitHub release.
The text was updated successfully, but these errors were encountered:
So as per my understanding the deployments needs to be handled via deploy.yml using ansible , currently it's done via pipeline yml file using manual push to do it .
Also do we have to also have some health checks in same ?
Seems interesting...let me know when we we are planning to implement it .@arkid15r
We have working setup for staging so the task is to replicate docker image build and deployment parts for production environment. The only difference will be the trigger -- we want to do it upon release publishing event.
Also don't we have a pr labeler for that ...something like Devops / deploy?
Is your feature request related to a problem? Please describe.
Our automated pipeline currently deploys to the staging environment at nest.owasp.dev. As the project evolves, it's time to establish a dedicated production environment for nest.owasp.org, which currently redirects to staging.
Describe the solution you'd like
Enhance CI/CD workflows, Docker configurations, Ansible playbooks, and any other necessary setups to enable automated deployments to the Nest production environment triggered by creating a GitHub release.
The text was updated successfully, but these errors were encountered: