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

Automatically deploy site content as appropriate #33

Open
1 of 3 tasks
anjackson opened this issue Jul 27, 2022 · 0 comments
Open
1 of 3 tasks

Automatically deploy site content as appropriate #33

anjackson opened this issue Jul 27, 2022 · 0 comments

Comments

@anjackson
Copy link
Contributor

anjackson commented Jul 27, 2022

Once the editorial workflow is clear, we could consider keeping the BETA site in sync with the most recent accepted changes to the ukwa-site.

This needs to be compatible with however we implement regularly-updated Target/Collection pages generated by Hugo from source data files.

Using a CI process would mean:

  • Install a GitLab runner on BETA, associated with this repo.
  • Move the service stack to an internal GitLab repo that gets mirrors to GitHub.
  • Add GitLab CI/CD hooks that use the BETA runner to refresh the ukwa-site image when it gets updated? Or when the stack is updated?
@anjackson anjackson changed the title Automatically deploy site updates to BETA Automatically deploy site content as appropriate Jun 8, 2023
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

1 participant