| @@ -3,15 +3,16 @@ |
| 3 |
3 |
**A small but mighty software forge that lives in your Git repository.** |
| 4 |
4 |
|
| 5 |
5 |
Vole is for developers who value ownership, simplicity, and resilience over feature |
| 6 |
|
count. Code, issues, change requests, approvals, releases, and CI records live in |
| 7 |
|
Git. Runners run where you put them. There is no control plane in a data center |
| 8 |
|
you do not own. |
|
6 |
count. Code, issues, change requests, approvals, and releases live in Git. CI |
|
7 |
history lives in the instance's database. Runners run where you put them. There is |
|
8 |
no control plane in a data center you do not own. |
| 9 |
9 |
|
| 10 |
10 |
## Why Vole |
| 11 |
11 |
|
| 12 |
|
- **Your repository survives outages.** Issues, reviews, approvals, releases, |
| 13 |
|
and build records clone with the code, so they are not trapped in a vendor's |
| 14 |
|
database. When a hosting service goes down, your repository does not. |
|
12 |
- **Your repository survives outages.** Issues, reviews, approvals, and releases |
|
13 |
clone with the code, so the work that belongs to the repository is not trapped |
|
14 |
in a vendor's database. CI history stays on your instance and is backed up with |
|
15 |
it. When a hosting service goes down, your repository does not. |
| 15 |
16 |
- **CI is not tied to a vendor.** Add a workflow, start a runner anywhere it can run |
| 16 |
17 |
an OCI runtime (Docker, rootless Podman, or nerdctl), and Vole sends it work over |
| 17 |
18 |
SSH. Your build machines can be a server, a spare desktop, or a box in the closet. |