Oasis CLI
Linux. Install with the one-liner, or download the binary directly.
Verify your download against the published hashes before installing.
e4a80fd1c1429a25875eb084771b464e9b5949884e0b63ad93efb4c1bd88507316f9b3cb2c66c1aee009d45485b948eb3956841b83f1b466a9797ece04d7c7615cac3106defc508f0fd60239cf1130e2d227b5978884e7fe562ae111a3d815018bdd4b9d20a4dbf0a1c5706930ac80c382efa89361ddb45de076f9899d0370a3538aa3fef91c19b776e0ca65a27211c0The installer takes an optional version argument. Passing 1.0.1 pins this exact build rather than the newest one, downloads it for your platform, and verifies it against the SHA-256 published in the release manifest.
curl -fsSL https://get.mutexer.com/oasis/install.sh | bash -s 1.0.1With no version argument the installer resolves the newest published release itself, so this command stays correct as new versions ship.
curl -fsSL https://get.mutexer.com/oasis/install.sh | bashDo not run the installer with sudo
Oasis CLI installs under your home directory and needs no root. Under sudo it installs into root's home instead of yours, and the oasis-agent command will not resolve in your own shell. The installer refuses sudo for this reason.
Once installed, the binary updates itself. This is the same code path the installer hands over to, so an upgrade and a fresh install do exactly the same work.
oasis-agent updateThe manifest for this version lists every platform build with its SHA-256, MD5, size, and download URL. It is what the installer checks against, and you can fetch it yourself.
curl -fsSL https://get.mutexer.com/oasis/1.0.1/manifest.jsoncurl or wget. The installer uses whichever it finds.