John Olheiser
045c0a6f60
Actually fix info page Signed-off-by: jolheiser <john.olheiser@gmail.com> Co-authored-by: jolheiser <john.olheiser@gmail.com> Reviewed-on: #5 |
||
|---|---|---|
| config | ||
| router | ||
| service | ||
| .gitignore | ||
| go.mod | ||
| go.sum | ||
| horcrux.example.go | ||
| horcrux.example.yml | ||
| main.go | ||
| Makefile | ||
| README.md | ||
Horcrux
Split your soul source code into multiple repositories.
This project was mostly a silly idea, but it seemed to have just enough use-case for me to seriously think about implementing.
The idea is, whenever you push changes to a remote, that remote sends
a webhook to horcrux, which then clones and pushes those changes
to any number of configured services.
For an example config, check out horcrux.example.yml
Webhook Endpoints
The format for a webhook endpoint is https://horcrux.domain.tld/<name>/<service> where name is the name of your
configured repository and service is the type of service sending the webhook. (gitea, github, or gitlab)
What if I want to replicate to multiple Gitea instances?
Create two configs for the same repository, with different names. Add a webhook for any alternate instance.
As you (or horcrux) pushes to an instance, it could kick off a webhook to any number of horcrux endpoints.
Examples
Check out this repository on