Daylog for GNU/Linux x64 with glibc

Daylog is a personal journal stored in a local SQLite database. Run it on a
trusted computer. The API and web client listen on 127.0.0.1 only.

Requires a glibc-based GNU/Linux x64 computer with an SSE4.2-capable CPU and
Node.js. This archive was built on glibc 2.39 with Node.js v26.8.1. Other
glibc and Node.js versions have not been tested. Bun and the source repository
are not needed to run it. Musl-only Linux distributions are not supported by
these binaries.

From the extracted daylog-linux-x64-glibc directory:

  node daylog.mjs --data-dir /absolute/path/to/private/daylog --check
  node daylog.mjs --data-dir /absolute/path/to/private/daylog

The first command initializes or checks your journal without starting servers.
The second opens the web client at http://127.0.0.1:5183 and the API at
http://127.0.0.1:3013. Press Ctrl-C to stop both. Repeat the command to keep
using the same journal. Existing compatible entries are preserved.

Without --data-dir, Daylog uses $XDG_DATA_HOME/daylog/local.db, or
~/.local/share/daylog/local.db. Do not place the data directory in a shared
folder. Keep your own backup of the database file.

The local journal remains at /. Open http://127.0.0.1:5183/home for the full
Daylog overview without changing your journal data.

Original third-party license, copyright and attribution material is retained
in notices/. inventory.json records the exact original bytes and versions.
BUN-LICENSE.md retains upstream linked-library and rebuilding information.

Runtime replacement

The application work is retained as api/index.js and api/init.js. bin/bun is
the genuine runtime separately from these bundles. To use a compatible Bun
built with modified libraries, replace bin/bun with your executable, retain
its executable permission, then run the same check/start commands. Keep the
original runtime and database backup so you can reverse the replacement.
This does not require publishing the private TypeScript repository. Original linked-library license and rebuilding information is in notices/.
Complete corresponding-source distribution and successful modified-library
rebuilding remain explicit unverified gates.
