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

ci(*): add website deployment logic #1103

Merged
merged 2 commits into from
Feb 3, 2023
Merged

ci(*): add website deployment logic #1103

merged 2 commits into from
Feb 3, 2023

Conversation

vdice
Copy link
Member

@vdice vdice commented Feb 2, 2023

  • Adds website deployment logic (auto on pushes to main; support for manual/ad hoc triggering as well)
  • Deploys to the prod version of the website on every push to main (once toggled below)
  • Removes unecessary logic from dispatch.yml workflow (previously used to coordinate deploys)

As noted in the added deploy/README.md, the website here has been redirect-based for some time, pointing to the official docs sub-site at https://developer.fermyon.com/spin (all content being in the fermyon/developer repo). However, until we sunset the classic domain (spin.fermyon.dev), I'd like to have this auto-deployment logic available for any potential website changes in the meantime (including transitioning to a Fermyon Cloud app when ready). We can remove the works after the classic domain has been removed.

Deployment (to canary) from initial PR version tested in: https://github.com/fermyon/spin/actions/runs/4068116760

TODO:

  • remove testing branch from deploy.yml
  • update to deploy to prod on merges to main

Signed-off-by: Vaughn Dice <vaughn.dice@fermyon.com>
Signed-off-by: Vaughn Dice <vaughn.dice@fermyon.com>
@vdice vdice merged commit 381b534 into main Feb 3, 2023
@vdice vdice deleted the vdice/website-deployment branch February 3, 2023 18:16
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

Successfully merging this pull request may close these issues.

None yet

2 participants