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

Create staging and production environments, and implement release strategy #13

Open
9 of 12 tasks
kabilar opened this issue Jan 22, 2024 · 0 comments
Open
9 of 12 tasks
Assignees

Comments

@kabilar
Copy link
Member

kabilar commented Jan 22, 2024

Create staging and production environments

  • LINC Archive
  • LINC CLI and Python API. We will use -i lincbrain-staging option for staging.
  • Enable SSL certificate on Heroku API staging account
  • Clear production database and bucket prior to launch

Release strategy

  • Staging
    • Every merge to the staging branch triggers a deployment by Netlify for the front-end and by GitHub Actions for the back-end
  • Production
    • Every merge to the release branch triggers a deployment by Netlify for the front-end
    • Every merge to the release branch followed by a workflow_dispatch triggers a deployment by GitHub Actions for the back-end
  • OAuth is conflating staging and production because of same root domain (i.e. lincbrain.org)

Documentation

  • Update docs on vendor accounts for creating a new environment from scratch
  • Update dandi-archive design doc with LINC release strategy

Testing

  • End-to-end user testing of staging and production environments (i.e. web app and CLI).
@kabilar kabilar changed the title Create staging environment and implement Kitware's release strategy for staging vs production Create staging and production environments, and implement release strategy Feb 13, 2024
@kabilar kabilar self-assigned this Feb 13, 2024
@kabilar kabilar transferred this issue from lincbrain/linc-infrastructure-old Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants