reseam/api
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description https://api.reseam.app
20 commits 1 branch 0 tags 1.5 MiB
  • TypeScript 99.3%
  • Dockerfile 0.7%
Find a file
Exact
Aunali321 e9fe3655f5 docs(api): fix stale config and endpoint claims, add docker compose
2026-09-05 22:19:45 +05:30
docs docs(api): fix stale config and endpoint claims, add docker compose 2026-09-05 22:19:45 +05:30
src fix(api): 304 on matching ETag, stale-on-error upstream, tag pruning, readable validation errors 2026-09-03 03:09:09 +05:30
test fix(api): 304 on matching ETag, stale-on-error upstream, tag pruning, readable validation errors 2026-09-03 03:09:09 +05:30
.gitignore feat: Initial commit 2026-04-17 00:46:48 +05:30
bun.lock fix(api): 304 on matching ETag, stale-on-error upstream, tag pruning, readable validation errors 2026-09-03 03:09:09 +05:30
docker-compose.yml docs(api): fix stale config and endpoint claims, add docker compose 2026-09-05 22:19:45 +05:30
Dockerfile ci: build+push only, watchtower handles deploy; surface build sha as version 2026-04-17 01:13:08 +05:30
drizzle.config.ts feat: Initial commit 2026-04-17 00:46:48 +05:30
package.json fix(api): 304 on matching ETag, stale-on-error upstream, tag pruning, readable validation errors 2026-09-03 03:09:09 +05:30
README.md docs(api): fix stale config and endpoint claims, add docker compose 2026-09-05 22:19:45 +05:30
tsconfig.json feat: Initial commit 2026-04-17 00:46:48 +05:30

README.md

Reseam API

Distribution metadata server for Reseam, a Rust APK patching engine.

Authors publish signed .reseam bundles and host a patches.json at a stable URL. This API reads that file (and a manager.json for manager binaries), caches it, and exposes it back out at /patches.json + /manager.json plus structured /v1 JSON endpoints. /patches/<tag>/<name> and /manager/<tag>/<name> 302-redirect to the upstream asset so clients only ever see *.reseam.app URLs. The manager and website are the consumers.

One instance fronts one bundle. Run multiple instances for multiple bundles. Signature verification happens in consumers: the API serves the public key but doesn't check signatures itself. The API holds a single secret: the admin token for announcement writes. Everything else is cached reads of upstream JSON.

Announcements are stored in SQLite behind bearer-authed write endpoints.

Running

bun install
bun run dev          # dev server with watch
bun test             # run tests
bun run typecheck    # tsc --noEmit
bun run db:generate  # generate migration from schema changes
bun run start        # production server

Docker

docker compose up -d

Config

Var Default
PORT 4000
PATCHES_URL https://git.reseam.app/reseam/patches/releases/download/latest/patches.json
MANAGER_URL https://git.reseam.app/reseam/manager/releases/download/latest/manager.json
PATCHES_BUNDLE_BASE_URL https://git.reseam.app/reseam/patches/releases/download
MANAGER_BINARY_BASE_URL https://git.reseam.app/reseam/manager/releases/download
ADMIN_TOKEN empty; announcement writes return 503
DB_PATH ./data/reseam.db
CACHE_TTL 300
ALLOWED_ORIGINS https://reseam.app,https://manager.reseam.app

PATCHES_URL / MANAGER_URL are the upstream release-asset URLs the API fetches from. PATCHES_BUNDLE_BASE_URL / MANAGER_BINARY_BASE_URL are where /patches/<tag>/<name> and /manager/<tag>/<name> redirect to; download URLs in patches.json should point at the API's redirect routes so end-clients only see *.reseam.app.

Announcement writes require Authorization: Bearer <ADMIN_TOKEN>.

All GET responses include Cache-Control and ETag headers. OpenAPI docs at /openapi.

Stack

Bun, Elysia, drizzle-orm on SQLite.