Linkstash local package
This Linux x64 glibc package includes the Linkstash web app, API, private SQLite initializer and native SQLite runtime. Install Node and Bun before starting; this package was built with Node 26.8.1 and Bun 1.4.2. `MANIFEST.json` lists the shipped file checksums. Your local installation stores its data on your machine. Human sign-in on a shared installation uses an administrator-configured OpenID Connect provider.
From the extracted `linkstash-local-linux-x64` directory, initialize a private data directory and start the app:
bun bin/local-db.js init --data-dir /absolute/private/linkstash
node bin/local-run.mjs --data-dir /absolute/private/linkstashOpen <http://127.0.0.1:5181/home> for the product home, then Open your library. A verified OIDC browser session at the root goes to `/app`; `/home` always stays public. The API listens on `127.0.0.1:3011`. Stop the supervisor with Ctrl-C. The database remains at `/absolute/private/linkstash/linkstash.db`; the initializer creates new data with private directory and file permissions and preserves entries on repeat. `bun bin/local-db.js check --data-dir /absolute/private/linkstash` verifies a prepared directory without serving the app. Back up an existing library before upgrading it, and stop the API while running `init`; the initializer adds only the session tables to a compatible populated database.
The default loopback installation uses one local library. Do not forward an unauthenticated local API through a reverse proxy. To enable human sign-in, register an OpenID Connect client with callback `http://127.0.0.1:3011/auth/callback` and set `LINKSTASH_OIDC_ISSUER`, `LINKSTASH_OIDC_CLIENT_ID`, and `LINKSTASH_OIDC_CLIENT_SECRET` in the shell that launches Linkstash. The launcher stores a random session signing key privately in the data directory and reuses it across restarts. The provider must permit the loopback callback. Server-owned bearer-key configuration remains available for automation.
This package targets the local ports above. Remote hosting requires an HTTPS deployment and verified customer access; this archive does not provide that deployment.