T

Aleksei Pavlov 325ebe7759 fix(zero): back to multipart photo upload (engine now has uploads volume)

The URL-mode I added earlier (Telegram fetches photo from our public URL)
hit 'wrong type of the web page content' from Telegram servers — likely
because traefik / Cloudflare serves something non-image to bot User-Agent,
or the worker proxy mangles things on the way back. Either way it stopped
working.

Today we added the persistent /var/www/zeropost-uploads volume to the engine
container, so the file is now directly accessible inside engine. Switching
back to multipart upload via fs.createReadStream — same pattern as
scheduledPostsRunner uses for article covers (and which works fine).

ZERO_PUBLIC_BASE_URL setting is no longer needed but harmless if left.

2026-06-20 10:26:13 +03:00

scripts

feat: Зеро-персонаж, auto-publish, auto-series, channel-stats, fallback covers

2026-06-07 14:03:56 +03:00

src

fix(zero): back to multipart photo upload (engine now has uploads volume)

2026-06-20 10:26:13 +03:00

.env.example

feat: initial zeropost-engine structure

2026-05-30 21:29:04 +03:00

.gitignore

feat: Зеро-персонаж, auto-publish, auto-series, channel-stats, fallback covers