~/code/myapp
myapp-x86_64
23.8 MiB
./myapp-x86_64
  • Ubuntu 20.04
  • Ubuntu 24.04
  • Debian 12
  • Fedora 45
  • Arch Linux
  • openSUSE
  • Linux Mint 22.3
  • namiOS

nami bundle, in nami 0.18.11

Ship your Linux app
as one file.

It runs on Ubuntu, Fedora, Debian, Arch and the rest, old and new, with nothing to install first. And it keeps itself up to date.

Every distribution

One file for old and new distributions.

A bundle carries everything the program needs, down to glibc. Only the graphics driver, fonts, locale and certificates come from the computer.

  • Ubuntu 20.04
  • Ubuntu 24.04
  • Debian 12
  • Fedora 45
  • Arch Linux
  • openSUSE Tumbleweed
  • Linux Mint 22.3
  • namiOS
Eight open-source apps, bundled once on Ubuntu 24.04, and where each started
AppUbuntu20.04Ubuntu24.04Debian12Fedora45Arch LinuxopenSUSETumbleweedLinux Mint22.3namiOS
Open SurgeGame · 225 MiBRunsRunsRunsRunsRunsRunsRunsRuns
simpRust, wgpu · 24 MiB–RunsRunsRunsRunsRunsRunsRuns
StrawberryQt 6 · 358 MiBRunsRunsRunsRunsRunsRunsRunsRuns
RnoteGTK 4 · 263 MiB–RunsRunsRunsRunsRunsRunsRuns
AmberolGTK 4 · 267 MiB–RunsRunsRunsRunsRunsRunsRuns
ElementElectron · 416 MiBRunsRunsRunsRunsRunsRunsRunsRuns
tmuxCommand · 14 MiBRunsRunsRunsRunsRunsRunsRunsRuns
aria2Command · 22 MiBRunsRunsRunsRunsRunsRunsRunsRuns
  • Open SurgeGame · 225 MiBAll eight
  • simpRust, wgpu · 24 MiBAll but Ubuntu 20.04
  • StrawberryQt 6 · 358 MiBAll eight
  • RnoteGTK 4 · 263 MiBAll but Ubuntu 20.04
  • AmberolGTK 4 · 267 MiBAll but Ubuntu 20.04
  • ElementElectron · 416 MiBAll eight
  • tmuxCommand · 14 MiBAll eight
  • aria2Command · 22 MiBAll eight

Eight open-source apps, each bundled once on Ubuntu 24.04, then started on each distribution. On Ubuntu 20.04's and Debian 12's older Mesa, Rnote's and Amberol's windows stay black on X11; a bundle made with --mesa draws.

Updates

Your app keeps itself up to date.

Publish a new version, and every copy downloads only what changed, signed with your key.

You publish a new version
$ nami bundle . --update-url github:ada/myapp --publish-dir release/
$ gh release create v1.2.0 release/*
Their copy updatesonce a day by itself, or now
$ ~/Apps/myapp-x86_64 --nami-bundle-update
/home/ada/Apps/myapp-x86_64: updated myapp from 1.1.0 to 1.2.0
downloaded 3 of its 38 parts (1.2 MiB, only what changed in each); the rest it had already
  • Only what changedEach copy looks once a day and downloads only what changed in each part. FeatherPad 1.6.4 is 72 MiB in place of 139 MiB.
  • Only from youA copy takes an update only if it's signed with your key.
  • At the next startThe new version takes over the next time the app opens, never while it runs.

Projects

Bundle your project as it is.

nami builds Rust, Go, C and C++, Python, Node.js, Electron, Zig, Flutter and .NET projects with its own tools, so you don't need a recipe or the tools installed.

  • RustCargo.toml
  • Gogo.mod
  • C and C++meson.build, CMakeLists.txt
  • Pythonpyproject.toml
  • Node.js, Electronpackage.json
  • Zigbuild.zig
  • Flutterpubspec.yaml
  • .NET.csproj
project.namionly what nami can't work out
bundle:
  name: myapp
  version: 1.2.0
  program: myapp
  icon: assets/myapp.svg
  desktop: assets/myapp.desktop
It also bundles
$ nami bundle ./packages/myapp                # a recipe folder
$ nami bundle jq                              # a package from the catalog
$ nami bundle ./target/release/myapp          # a program you built
$ nami bundle myapp-1.0-linux-x86_64.tar.gz   # a release tarball

Releases

A bundle with every release.

Add nami-bundle-action to your workflow. Push a tag such as v1.2.0, and the release gets myapp-x86_64 and its .sha256 file.

.github/workflows/release.yml
name: Release
on:
  push:
    tags: ['v*']
permissions:
  contents: write
jobs:
  linux:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - uses: jensbirk/tray/action@main
  • One link to the newestThe file's name has no version, so releases/latest/download/myapp-x86_64 always points at the newest.
  • One click on namiOSOn namiOS, a downloaded bundle opens in Settings, ready to install, like a .deb.

Compare

How it compares.

Each way of shipping a Linux app makes a trade. Here's where a bundle stands next to AppImage and Flatpak.

Featurenami bundleAppImageFlatpak
Needs nothing installedYesNeeds FUSENeeds Flatpak
Works on old and new distributionsCarries its own glibcUses the computer's glibcThrough its runtimes
Updates itself with only what changedYesWith AppImageUpdateThrough Flatpak
Signed updatesWith your keyOptionalYes
SandboxOptional–Yes
SizeBiggest: everything, down to glibcSmaller: uses the computer's librariesRuntimes shared between apps

Need an AppImage as well? nami bundle --appimage writes one beside the bundle.

Limits

Know the limits.

A bundle is made for one kind of computer, and it's bigger than a package.

  • Made for x86_64 and glibcNot musl distributions like Alpine. On ARM, --arch aarch64 bundles command-line programs from the catalog, without updates for now.
  • Sandboxed only if you say soAnd only where the computer has bubblewrap. Otherwise a bundle runs with the person's rights. Bundle only software you may hand out.
  • Bigger filesIt carries every file the program refers to. With --thin, the common parts download on the first start.
  • A slower first startThe first start unpacks what isn't there yet, a few seconds for a GTK app. /tmp must be writable.
BundleFileUnpacked
jq10.4 MiB37.6 MiB
featherpadQt 6143 MiB729 MiB
gnome-text-editorGTK 4264 MiB964 MiB

All bundles unpack into one shared store, so GTK or glibc is on the disk once, however many bundles carry it.

Install

Start shipping with nami.

nami bundle comes with nami. Paste this into a terminal on any distribution on x86_64, then run nami bundle in your project.

$ curl -fsSL https://namios.dev/install | sh

alphanami is alpha software: most things work, some may not yet, and you can undo every change.

Other downloads: tarball · checksums

Install nami, step by step

Every option, step by step: Ship your app