Skip to content

web: run a public deployment of the latest release in --read-only mode #1432

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

Open
sudoforge opened this issue May 16, 2025 · 0 comments
Open
Assignees
Labels
area/infra Relates to git-bug's infrastructure kind/feature Relates to a new feature priority/backlog Higher priority than priority/awaiting-more-evidence

Comments

@sudoforge
Copy link
Contributor

sudoforge commented May 16, 2025

instead of including many independent screenshots of the web UI, we should host it so that users can browse git-bug issues with the latest release of the web ui to experience what it's like.

this deployment would be unauthenticated, and only expose the web ui in read-only mode.

it should:

  • leverage anubis for request filtering
  • be in a private network, exposed via a load balancer
  • auto scale based on load to some reasonable amount (we won't scale infinitely, but we should configure a modest upper limit to handle surge traffic, e.g. from HN or TLDR posts)
  • be immutable - build the image in a pipeline, block all non-http(s) traffic
  • periodically run git bug pull to stay up-to-date
  • be updated as part of the release pipeline (perhaps a second deployment for HEAD in the future)

it does not need any authentication to pull from the https remote.

@sudoforge sudoforge added area/pipelines Relates to pipelines kind/feature Relates to a new feature priority/backlog Higher priority than priority/awaiting-more-evidence area/infra Relates to git-bug's infrastructure and removed area/pipelines Relates to pipelines labels May 16, 2025
@sudoforge sudoforge changed the title run the webapp on a public domain web: run a public deployment of the latest release in --read-only mode May 16, 2025
@sudoforge sudoforge self-assigned this May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra Relates to git-bug's infrastructure kind/feature Relates to a new feature priority/backlog Higher priority than priority/awaiting-more-evidence
Projects
None yet
Development

No branches or pull requests

1 participant