PLV is currently in pilot. Builds include the plv client,
the plvserver admin tool, and the plvserverweb
API server.
Step 1
PLV supports all major Operating Systems. Pick the one you want to user below to get started.
Inno Setup installer with component selection (Client, Server,
Website, or Full). Server installs configure a Windows service and
the PlvDeploy rollout tool that activates a stable
current/ tree under C:\Program Files\PipelineVCS.
Installer Package (.pkg) for Apple Silicon. Installs
under /Library/PipelineVCS with launchd
services for the server and optional website. Intel Macs are not
supported in this release.
Versioned tarball with install.sh for host installs
under /opt/pipelinevcs, plus a systemd
unit template. A container image is also available with both
plvserver and plvserverweb baked in.
What's inside
The client CLI. Talks to a PLV server, manages local checkouts, refs, branches, composites, locks, and PRs. All major work is done here.
Server admin tool. setup, config, fsck, log verification, repo administration, and backup orchestration.
The web portal. Is a GUI for managing your PLV server. Has pages to browse users, repos, PRs, issues, releases, etc.
Step 2 (optional)
You can use the client against any PLV server. To run your own, install the server component or pull the container image.
# run the installer and select Server (or Full). # After install, configure with elevated PowerShell: plvserver setup plvserver config creation orgs=true repos=true repo_limit=15 Get-Service PipelineVCS
# After installing the .pkg: sudo plvserver setup sudo launchctl load /Library/LaunchDaemons/com.pipelinevcs.server.plist sudo launchctl print system/com.pipelinevcs.server
# extract the release tarball, then: sudo ./install.sh sudo plvserver setup sudo systemctl enable --now pipelinevcs.service sudo systemctl status pipelinevcs.service
docker volume create pipelinevcs-data docker run --rm -it \ -v pipelinevcs-data:/var/lib/pipelinevcs \ pipelinevcs:0.1.0 \ plvserver setup docker run -d --name pipelinevcs \ -p 49508:49508 \ -v pipelinevcs-data:/var/lib/pipelinevcs \ pipelinevcs:0.1.0
Step 3
plv connect https://your-plv-host
plv create repo path=./my-app server=https://your-plv-host name=my-app
plv state
plv commit message="Initial import"
plv push
Verify
Every release publishes a manifest.json with BLAKE3
hashes for each artifact. Verify the installer matches before running it.
:: download b3sum.exe: curl -L -o b3sum.exe https://github.com/BLAKE3-team/BLAKE3/releases/latest/download/b3sum_windows_x64_bin.exe :: verify the installer: b3sum.exe plv-0.1.0-win-x64.exe :: compare against the published manifest: :: manifest.json -> entries[].path + entries[].blake3
# download b3sum.exe: Invoke-WebRequest -Uri https://github.com/BLAKE3-team/BLAKE3/releases/latest/download/b3sum_windows_x64_bin.exe -OutFile b3sum.exe # verify the installer: .\b3sum.exe plv-0.1.0-win-x64.exe # compare against the published manifest: # manifest.json -> entries[].path + entries[].blake3
# install b3sum once: brew install b3sum # verify the installer: b3sum plv-0.1.0-osx-arm64.pkg # compare against the published manifest: # manifest.json -> entries[].path + entries[].blake3
# install b3sum once: sudo apt install b3sum # verify the installer: b3sum plv-0.1.0-linux-x64.tar.gz # compare against the published manifest: # manifest.json -> entries[].path + entries[].blake3
Requirements
.pkg. Server installs use launchd and require an admin password.
systemd for the host install, or any container runtime for the Docker image.