Affine Pro is outdated

[xenstar]

Template Name

Affine Pro

Relevant Logs of the Error

The template fetches the version from here, but it's not working anymore

ghcr.io/toeverything/affine-graphql:stable-780dd83

Here is the issue after deployment:

Steps to Reproduce the Error

1, Added the template
2. Click on Deployment
3. Have the error

Environment Information

VPS Provider: Onidel
Dokploy: Version: v0.28.8

When does this error occur?

During template deployment

Additional Context

No response

Will you send a PR to fix it?

No

[dosubot]

Hi @xenstar! I'm Dosu and I’m helping the templates team.

The Affine Pro template currently pins both the main affinepro service and the migration service to ghcr.io/toeverything/affine-graphql:stable-780dd83 [1], and the same version is set in meta.json [2]. That image tag appears to no longer be available upstream, which is what's causing the deployment failure.

To fix this, someone would need to:

1. Find a valid current tag from the AFFiNE GHCR packages (e.g., a newer stable-* tag).
2. Update ghcr.io/toeverything/affine-graphql:stable-780dd83 → the new tag in both services in blueprints/affinepro/docker-compose.yml [3].
3. Update the version field in meta.json to match the new tag [2].
4. Run npm run process-meta [4].
5. Verify the image exists with docker manifest inspect ghcr.io/toeverything/affine-graphql:<new-tag> and test the deployment before submitting a PR.

As a temporary workaround, you can manually update the image tag in the Dokploy service settings after deploying the template — replace stable-780dd83 with a valid tag from the upstream registry for both the main and migration services.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[xenstar]

Yes, the templates need to be updated, and also, Cloudflare R2 is mandatory. I was looking to add the dokploy volume disk. I think if the dokploy team works on it, it can be fixed instantly.