Skip to content

v0.1.0-alpha.2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 31 Oct 20:37
· 470 commits to main since this release

The test bot moves onto production's database, so a person has one history
on both sites, and each bot still works only its own jobs and chats. The
backend for several results from one press comes with it. Deploy production
first; the test bot's stack follows (Breaking).

Known Limitations

  • The framy schema still has no backups (#28).
  • The site does not send several results from one press yet: the API is
    there, the composer that uses it comes next.

Changed

  • The test bot and production share one database: the framy schema in
    core-postgres. A person sees the same history, settings and connected keys
    on framy.ws04.cc and framy-test.ws04.cc, and the free tier's daily budget
    is counted once over both bots instead of once on each.
  • Each bot works only its own jobs and tells only its own chats. A job runs
    on the bot whose chat or site started it, and a result made on a site goes
    to the DM from that site's bot. Inline mode, replies to a result, albums
    and Send to Telegram use only what the bot itself sent or saw, since a
    Telegram file id works only for the bot that got it.
  • The catalog sync, the currency rates, the sweep of uploads no job took,
    the thumbnails and the operator chat run on production only. The test bot
    shows production's catalog, so a catalog change reaches it with the
    release that takes it to production.

Added

  • FRAMY_STACK names the bot when two share one schema: empty for
    production, test for the test bot. A stack other than production puts its
    name before its River queues and its Telegram dedupe keys.
  • Several results from one press, each with its own model and settings
    (POST /api/batches). framy decides how many requests that is: frames
    that are the same run go together, as many as the model makes at once,
    so five pictures where a model makes four at once are two requests, four
    and one. A press is queued whole or not at all, and the history keeps it
    as one run. A quote with batch: true says which frames go together and
    what the press costs.

Breaking

  • Migration 029_stack.sql marks jobs, chat runs and album items with their
    bot and changes the album cache's key. v0.1.0-alpha.1 cannot write the
    album cache after it, so a rollback past this release loses albums sent
    until the next deploy.
  • Deploy production first. The test bot's stack then moves onto
    core-postgres: FRAMY_STACK=test, DATABASE_URL as framy_core, the
    network core_net, production's KEK in secrets/kek, no R2_PREFIX
    (deploy/ws04-test/compose.yaml). Its own PostgreSQL goes; its data is not
    moved, and the volume stays.
  • The test bot runs dev and applies its migrations to production's schema
    before production does, so every migration from now on is additive
    (AGENTS.md, Migrations).

Fixed

  • Switching an empty composer from Image to Video no longer flashes the
    hint of the row of files at the left edge of the page, one word to a
    line.

Container image

ghcr.io/freshlabdev/framy@sha256:8059abf692efd02e00764fd372dbf60b9bee30a72df9eee0632f6a917911b6bc