https://github.com/geirsagberg/github-deploy-center
Static website for visualizing and performing deploys using GitHub Actions
https://github.com/geirsagberg/github-deploy-center
deployment github-actions
Last synced: about 1 month ago
JSON representation
Static website for visualizing and performing deploys using GitHub Actions
- Host: GitHub
- URL: https://github.com/geirsagberg/github-deploy-center
- Owner: geirsagberg
- License: mit
- Created: 2020-10-24T23:09:13.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2026-04-28T15:06:53.000Z (about 2 months ago)
- Last Synced: 2026-04-28T16:10:00.262Z (about 2 months ago)
- Topics: deployment, github-actions
- Language: TypeScript
- Homepage: https://githubdeploy.z1.web.core.windows.net/
- Size: 56.4 MB
- Stars: 22
- Watchers: 1
- Forks: 6
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# GitHub Deploy Center (GDC)
GDC is a static website for showing your GitHub releases and deployments, and provides one-click deployment to any environment, powered by -your- GitHub Action workflows.
- GDC is a fully static website and uses only local storage. No cookies, and nothing is sent to any server!
- Application settings can be exported, shared and imported.
- Monorepos are supported, with a flexible configuration flow for multiple applications in the same repo.
## Getting started
To use GDC, you need a couple of things:
- A GitHub Personal Access Token with the `repo` OAuth scope. You can create one [here](https://github.com/settings/tokens).
- A way to create GitHub releases (preferrably automatically, e.g. through GH Actions). See [the GDC Build and Publish workflow](./.github/workflows/build-and-publish.yml) as an example.
- A GitHub Workflow for **deployment** with the `workflow_dispatch` trigger.
- The workflow must accept the following inputs (names are customizable):
- `ref`: Which release version to deploy (e.g. v1.0.3)
- `environment`: Which environment to deploy to (e.g. dev, test or prod)
- The workflow must create a deployment for the same commit as the release, and update status on success or failure.
- RECOMMENDED: If you create the deployment with the `payload` of `{"workflow_run_id": ${{ github.run_id }}}`, the deployment will be linked to the workflow run in the UI.
- See [the GDC Deploy workflow](./.github/workflows/deploy.yml) as an example.
## Hosting
The app is hosted in Azure at https://githubdeploy.z1.web.core.windows.net/, and will be kept updated to the latest version. If you want to host it yourself, you can build it for production with `bun run build`, then host the resulting static assets in `dist/` anywhere you like, e.g. Azure Blob Storage, Heroku, Google Cloud Storage.
# Development
The app is built with:
- [Vite](https://vitejs.dev/)
- [Material UI](https://material-ui.com/)
- [Valtio](https://valtio.dev/)
- [React Query](https://@tanstack/react-query.tanstack.com/)
- [GraphQL](https://graphql.org/)
## Start locally
```
bun install
bun run start
```