Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed deployment workflow #18

Open
viktorix opened this issue Nov 24, 2022 · 0 comments
Open

Proposed deployment workflow #18

viktorix opened this issue Nov 24, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@viktorix
Copy link
Member

In order to simplify things but also keep everything secure and accessible, here's my proposed deployment workflow:

  1. staging is the main working branch, which is synced to the staging website. We use it to test changes.
  2. When you need to test changes in the staging branch, you can SSH into the server and git pull to get the changes.
  3. When everything is ready and needs to be deployed, create a PR to merge staging with production.
  4. At this point git pull in the right directory will sync production branch on the server. production branch is protected.

We may automate step 4 using GitHub Actions to deploy code automatically once changes are made to the production branch. This will expedite the process and can also help reduce access to sensitive server credentials.

@viktorix viktorix added the enhancement New feature or request label Nov 24, 2022
@viktorix viktorix pinned this issue Nov 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant