asepharyana d296e0ebcf fix(upload): wrap gzip chunk output in Buffer so Telegraf uploads work
Root cause of '400: Bad Request: there is no document in the request' on
chunked uploads of compressible files (MP4, zip, text, etc.):
Bun.gzipSync() returns a plain Uint8Array, NOT a Buffer. Telegraf
(sendDocument/sendVideo) only recognises Buffer/Blob/stream sources as
file uploads — a plain Uint8Array produces an empty multipart body and
Telegram rejects the request.

Verified via isolated forwardToStorage probes:
- raw Buffer chunk (.bin, MP4) -> OK
- plain Uint8Array chunk -> FAIL: there is no document
- Buffer.from(gzip) chunk -> OK (after fix)
- .gz extension on Uint8Array did NOT help (rules out MIME/extension)

This only affected chunked uploads of compressible files; incompressible
files (random .bin) worked by accident because gzip didn't shrink them so
the raw Buffer was forwarded unchanged.
2026-09-06 00:11:00 +07:00

Telegram Bot Uploader Backend

Backend production-ready untuk upload file ke Telegram yang tersimpan di private channel.

Setup

  1. Siapkan PostgreSQL database (produksi: database uploader via PgBouncer pool di 100.121.180.82:6432)
  2. Setup environment: cp .env.example .env
  3. Edit .env dengan nilai yang sesuai (lihat DATABASE_URL, PORT=4000)
  4. Create table: bun run db:migrate
  5. Install dependencies: bun install

Telegram Private Channel Setup

  1. Buat private channel Telegram
  2. Tambah bot sebagai admin di channel
  3. Dapatkan STORAGE_CHANNEL_ID (misalnya -1001234567890)

Running

bun run dev      # Development mode
bun run start    # Production mode

Deployment (Produksi — Nix + systemd)

Infra lama berbasis Docker + Traefik sudah dihapus dari orangevps (2026-08-02).

  • Host: orangevps
  • Service: systemd unit teleuploader (env via /etc/teleuploader/env / BWS secrets)
  • Build: Nix flake (flake.nix) — nix build .#teleuploader → nix copy → systemctl restart teleuploader
  • CI: .github/workflows/deploy.yml (Gitea Actions / GitHub Actions)
  • Port: 4000 (PORT env)
  • Domain: https://upload.asepharyana.my.id
  • Reverse proxy: Caddy (bukan Traefik/Docker)
  • Database: postgresql://asephs:***@100.121.180.82:6432/uploader (PgBouncer pool di imrnes, bukan 5432/localhost)
  • deploy.sh & Dockerfile & docker-compose.yml bersifat legacy — jangan dipakai untuk deploy produksi.

API Endpoints

  • POST /api/upload - Upload file
  • GET /f/:public_id - Download redirect
  • GET /file/:public_id/info - File metadata
  • GET /health - Health check

FAQ

URL permanen maksudnya apa? URL backend tetap permanen: https://upload.asepharyana.my.id/f/{public_id} Ini berarti URL service Anda fix, bukan jaminan file Telegram abadi.

Testing

Gunakan bot Telegram untuk upload, atau upload API langsung via HTTP.

S
Description
FileDrop Telegram-backed S3-compatible uploader
Readme
1.3 MiB
Languages
TypeScript 93%
HTML 3.8%
Shell 1.7%
JavaScript 0.7%
Nix 0.6%
Other 0.2%