Skip to content

Commit

Permalink
docs(dev): document manual bioconda fork update
Browse files Browse the repository at this point in the history
  • Loading branch information
ivan-aksamentov committed Nov 5, 2024
1 parent 6489d24 commit 2212974
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions docs/dev/developer-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -447,6 +447,18 @@ Nextclade build and deployment process is automated using GitHub Actions:
The workflows run on every pull request on GitHub and every push to a major branch.
> Hint if the bioconda release job fails due to push permissions:
>
> You need to update the `nextstrain/bioconda` fork manually in order to be
>
> Clone the fork https://github.com/nextstrain/bioconda-recipes as described in the readme. Follow the instructions precisely, don't invent anything new. Then push the latest updates from the upstream to the fork with this command:
>
> ```
> cd biooconda-recipes && git push nextstrain bioconda/master:master
> ```
>
> Then go to the failing job and restart it.
### Deployment environments
Nextclade GitHub repository contains 3 major branches with special meaning: `master`, `staging` and `release`, each has a corresponding domain name for Nextclade Web. Nextclade built from one of these branches fetches datasets from the corresponding dataset deployment environment (See [Dataset server maintenance guide](https://github.com/nextstrain/nextclade_data/blob/master/docs/dataset-server-maintenance.md))
Expand Down

0 comments on commit 2212974

Please sign in to comment.