Skip to content
infinidysk

Prebuilt Linux archives1.x

since 0.10.0

Prebuilt release archives run infinidysk directly on Linux without Docker or a source build. They include the compiled backend, frontend, production Node.js dependencies, and rapidyenc native library.

Archives follow the same release channels and tags as the Docker image: stable builds below, rc and dev builds under Pre-release testing.

Requirements

Section titled “Requirements”
  • Linux x64 or ARM64
  • Node.js 24 or newer
  • ASP.NET Core Runtime 10
  • curl

The .NET SDK, CMake, Ninja, npm install, and Git submodules are not required.

Install

Section titled “Install”

Download the archive for your system from the latest GitHub release:

  • infinidysk-v<version>-linux-x64.tar.gz
  • infinidysk-v<version>-linux-arm64.tar.gz

Extract it and start the launcher:

Terminal window
tar -xzf infinidysk-v<version>-linux-<architecture>.tar.gz
cd infinidysk-v<version>-linux-<architecture>
./run.sh

Open http://localhost:3000. The launcher starts the frontend, applies database migrations, starts the backend, and stops both processes together.

By default, persistent state is stored in config/ inside the extracted directory. Set an external path for easier upgrades:

Terminal window
CONFIG_PATH=/var/lib/infinidysk ./run.sh

Other container environment variables are supported, including PORT, LOG_LEVEL, and the headless Settings overlay.

Pre-release testing

Section titled “Pre-release testing”

Each release candidate gets a versioned GitHub Pre-release and archives such as infinidysk-v0.10.0-rc.1-linux-x64.tar.gz. Those versioned pre-releases and their image tags are removed automatically when the next stable release ships.

For automation, the rolling rc pre-release always exposes stable asset URLs:

The archive’s version.txt identifies the exact release candidate. The rolling rc release remains after a stable release ships (it is not deleted), so check its version before assuming it is newer than latest.

Work-in-progress dev snapshots follow the same pattern on the rolling dev pre-release:

dev builds are unversioned, refresh whenever the maintainer validates a snapshot on non-production, and may be non-functional — see Release channels and tags.

Upgrade

Section titled “Upgrade”
  1. Stop the running launcher.
  2. Back up the directory selected by CONFIG_PATH.
  3. Download and extract the new archive into a new directory.
  4. Start its run.sh with the same CONFIG_PATH.

Do not copy the old backend/, frontend/, or node_modules/ directories into the new release.