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.

Sign up for GitHub

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

chore: update README.md with more information for deploying process #307

Merged
merged 2 commits into from
Feb 6, 2024
Merged

chore: update README.md with more information for deploying process #307

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3449fdb
chore: update README.md with more information for deploying process
alexruzenhack Jan 18, 2024
4d96729
chore: migrate Deployment section to SOP
alexruzenhack Jan 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,4 @@ If you add a new API, be careful to add ```request.header.origin``` as cacheKey,

## Deploying

Deploys are automated using Github Actions and Flux.

To deploy to the `testnet` environment, simply commit to the `main` branch.

To deploy to the `mainnet` environment, create a release in Github using a tag in the format `v0.0.0`

Currently we do not have an automated mechanism to be warned if some automated deployment fails. So, after triggering the deploy, you should check if a commit was made by `fluxcdbot` in https://github.com/HathorNetwork/ops-tools/commits/master, updating the project's manifests with the new Docker image tag.
See in the [SOP](https://github.com/HathorNetwork/ops-tools/blob/master/docs/sops/hathor-explorer-service.md#deployment).
Loading