mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
33 lines
639 B
YAML
33 lines
639 B
YAML
version: build-{build}.{branch}
|
|
|
|
clone_folder: C:\gopath\src\github.com\pkg\errors
|
|
shallow_clone: true # for startup speed
|
|
|
|
environment:
|
|
GOPATH: C:\gopath
|
|
|
|
platform:
|
|
- x64
|
|
|
|
# http://www.appveyor.com/docs/installed-software
|
|
install:
|
|
# some helpful output for debugging builds
|
|
- go version
|
|
- go env
|
|
# pre-installed MinGW at C:\MinGW is 32bit only
|
|
# but MSYS2 at C:\msys64 has mingw64
|
|
- set PATH=C:\msys64\mingw64\bin;%PATH%
|
|
- gcc --version
|
|
- g++ --version
|
|
|
|
build_script:
|
|
- go install -v ./...
|
|
|
|
test_script:
|
|
- set PATH=C:\gopath\bin;%PATH%
|
|
- go test -v ./...
|
|
|
|
#artifacts:
|
|
# - path: '%GOPATH%\bin\*.exe'
|
|
deploy: off
|