Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

Docs: self-hosting compose generator missing worker-executions service (1.9.0)Β #3056

Description

@scottgrobinson

πŸ’­ Description

Area: Self-hosting β†’ Docker Compose generator (src/lib/components/compose-generator/composeData.ts).

The generated self-hosting docker-compose.yml is missing the appwrite-worker-executions service introduced in Appwrite 1.9.0.

In 1.9.0, execution persistence moved to a dedicated executions worker (entrypoint worker-executions, Appwrite\Platform\Workers\Executions) that consumes the v1-executions queue and writes the execution document. The generated compose only includes the schedule-executions scheduler β€” there is no worker-executions service β€” so nothing drains v1-executions. On self-hosted installs this means:

  • Scheduled executions are never recorded.
  • Async executions get stuck in status: waiting forever.
  • Synchronous executions still work (the API persists them inline), which masks the problem.

The queue silently accumulates (~46k stranded jobs observed on an affected instance). Adding the worker drains the backlog and executions persist as completed.

Fix: add the appwrite-worker-executions service to the compose generator β€” PR #3055.

Note: the same omission exists in the main appwrite/appwrite compose template (app/views/install/compose.phtml), which likely needs a matching fix.

(Replaces #3054, opened with the wrong template.)

πŸ‘€ Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏒 Have you read the Code of Conduct?

Activity

  1. anurag629 commented on Jul 21, 2026

    @anurag629

    Can I work on this?

    The report looks right to me. The generator never emits appwrite-worker-executions, so on a self-hosted 1.9.0 install nothing consumes the v1-executions queue and async executions sit in waiting.

    I'd add the missing service to the generator data so the output matches the reference docker-compose.yml for 1.9.0, following the same pattern as the other worker entries rather than inventing a new one.

    Two questions first:

    1. The worker only exists from 1.9.0 onward. Should the generator add it only for that version and later, or does it just target the current release?
    2. Are any other services missing? If the data has drifted by more than this one entry, I'd rather fix it in one pass than file a follow-up for each.

    I'll post in #maintainers on Discord too, per the contributing guide.

  2. scottgrobinson commented on Jul 21, 2026

    @scottgrobinson
    Author

    @anurag629 There are already two PRs on the above.

  3. anurag629 commented on Jul 21, 2026

    @anurag629

    Sorry, ignore my comment above. I missed that #3055 is already open and fixes this. Leaving it to @scottgrobinson.

  4. eldadfux commented on Sep 21, 2026

    @eldadfux
    Member

    Starting today this repo is archived. Please raise any issues with the new Appwrite website on the main platform repo: https://github.com/appwrite/appwrite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions