Skip to content
Ashlane

Documentation, last updated 28 October 2026

Quickstart: your first patch in twenty minutes

You will install the ash command-line tool, push a build directory as release 0.1.0, and download it again with a verified install. You need an Ashlane account and a build folder.

  1. Install the CLI

    Version 2.9.1 is a single static binary for Linux, macOS and Windows.

    curl -fsSL https://n74.assetlines.net/install.sh | sh
    ash --version
    # ash 2.9.1 (chisel 2.9.0)
  2. Sign in and create a title

    The first command opens a browser to approve the device. A title is the unit you bill, roll out and sign for; use a short slug.

    ash login
    ash title create hollowmere --name "Hollowmere"
  3. Point at your origin

    Either let Ashlane Vault hold the files, or give us read-only credentials for an S3-compatible bucket. Playtest includes 50 GB of Vault.

    ash origin set hollowmere --vault
    # or: ash origin set hollowmere --s3-bucket studio-builds --prefix hollowmere --region eu-west-1
  4. Push a build

    The first push uploads everything. Later pushes upload only new chunks and compute deltas against the previous release on the channel.

    ash push ./build/win64 --title hollowmere --version 0.1.0 --channel beta
    # 1,204 files, 18.4 GB, 291,880 chunks
    # uploaded 18.4 GB in 6m12s, manifest signed with key k-2026-03
  5. Release it

    Channels start at 0%. Move players across gradually, or set 100% for an internal build.

    ash rollout set hollowmere beta --percent 10
    ash rollout status hollowmere beta
Stuck? Run ash doctor. It checks DNS, TLS and clock skew from your machine, and prints a block you can paste into a ticket to support.

Where to go next