[GH-ISSUE #777] Affine Pro is outdated #3675

Open
opened 2026-04-30 06:31:29 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @xenstar on GitHub (Apr 8, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/777

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

Image

Here is the issue after deployment:

Image

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

Originally created by @xenstar on GitHub (Apr 8, 2026). Original GitHub issue: https://github.com/Dokploy/templates/issues/777 ### 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 <img width="977" height="749" alt="Image" src="https://github.com/user-attachments/assets/bcf2c0fc-5209-484f-8891-daf18ec20dac" /> **Here is the issue after deployment:** <img width="1099" height="781" alt="Image" src="https://github.com/user-attachments/assets/05d7ddc7-3616-411e-af2d-24284e2ae796" /> ### Steps to Reproduce the Error 1, Added the template 2. Click on Deployment 3. Have the error ### Environment Information ```bash 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
GiteaMirror added the bug label 2026-04-30 06:31:29 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Apr 8, 2026):

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.

Leave Feedback Ask Dosu about templates Share Dosu with your team

<!-- gh-comment-id:4205411148 --> @dosubot[bot] commented on GitHub (Apr 8, 2026): <!-- Greeting --> Hi @xenstar! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the templates team. <!-- Answer --> The Affine Pro template currently pins both the main `affinepro` service and the `migration` service to `ghcr.io/toeverything/affine-graphql:stable-780dd83` [[1]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/affinepro/docker-compose.yml#L4), and the same version is set in `meta.json` [[2]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/meta.json#L108-L124). 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](https://github.com/toeverything/AFFiNE/pkgs/container/affine-graphql) (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]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/affinepro/docker-compose.yml). 3. Update the `version` field in `meta.json` to match the new tag [[2]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/meta.json#L108-L124). 4. Run `npm run process-meta` [[4]](https://app.dosu.dev/6bf07378-6531-485c-acb5-f8edab4b0c01/documents/607ba7f6-a597-4b27-bfae-d763edb9010b). 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. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=Dokploy%2Ftemplates).* --- Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=Dokploy%2Ftemplates). [![Leave Feedback](https://img.shields.io/badge/Leave%20Feedback-555555?style=flat)](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=Dokploy%2Ftemplates#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015) [![Ask Dosu about templates](https://img.shields.io/badge/Ask%20Dosu%20about%20templates-2f7b3f?style=flat&logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPHN2ZyB3aWR0aD0iODYiIGhlaWdodD0iODkiIHZpZXdCb3g9IjAgMCA4NiA4OSIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj48cGF0aCBkPSJNNS4yOTIzNiAxMi43OTI4TDE3Ljc1OTMgNi42ODE4OFY3Mi41NjY3TDUuMjkyMzYgODQuMDYxOFYxMi43OTI4WiIgZmlsbD0iI0I0QkI5MSIvPjxwYXRoIGQ9Ik0xOC4yNTc1IDczLjExOTZMNTkuMTMyOSA3Mi43NDhMNTEuNzAxMSA4Mi40MDk1TDI5LjAzMzggODYuMjkxTDYuMjM5NjIgODUuMTU1NEwxOC4yNTc1IDczLjExOTZaIiBmaWxsPSIjNzc4NTYxIi8%2BPHBhdGggZD0iTTE3LjQ5MTYgMy43MzYzM0wzLjU4NTU3IDEyLjcwOTlWODMuNTc5MkMzLjU4NTU3IDg0Ljc1NDIgNC45ODU2MyA4NS4zNjUyIDUuODQ3MDUgODQuNTY2TDE5LjYyOTYgNzEuNzgwMSIgc3Ryb2tlPSJibGFjayIgc3Ryb2tlLXdpZHRoPSI2LjQyODQ0IiBzdHJva2UtbGluZWNhcD0icm91bmQiLz48bWFzayBpZD0iZG9zdS1kLWN1dG91dCIgZmlsbD0id2hpdGUiPjxwYXRoIGZpbGwtcnVsZT0iZXZlbm9kZCIgY2xpcC1ydWxlPSJldmVub2RkIiBkPSJNNDAuNzA0IDAuNTE4MDY2SDE3LjA0MzlWNzYuMjIyMUg0MC43MDRINDIuNTgwNUg0Ny44MDEzQzY4LjcwNjQgNzYuMjIyMSA4NS42NTMzIDU5LjI3NTIgODUuNjUzMyAzOC4zNzAxQzg1LjY1MzMgMTcuNDY1IDY4LjcwNjMgMC41MTgwNjYgNDcuODAxMyAwLjUxODA2Nkg0Mi41ODA1SDQwLjcwNFoiLz48L21hc2s%2BPHBhdGggZmlsbC1ydWxlPSJldmVub2RkIiBjbGlwLXJ1bGU9ImV2ZW5vZGQiIGQ9Ik00MC43MDQgMC41MTgwNjZIMTcuMDQzOVY3Ni4yMjIxSDQwLjcwNEg0Mi41ODA1SDQ3LjgwMTNDNjguNzA2NCA3Ni4yMjIxIDg1LjY1MzMgNTkuMjc1MiA4NS42NTMzIDM4LjM3MDFDODUuNjUzMyAxNy40NjUgNjguNzA2MyAwLjUxODA2NiA0Ny44MDEzIDAuNTE4MDY2SDQyLjU4MDVINDAuNzA0WiIgZmlsbD0iI0YzRjZGMSIvPjxwYXRoIGQ9Ik0xNy4wNDM5IDAuNTE4MDY2Vi02LjU3OTE5SDkuOTQ2NjlWMC41MTgwNjZIMTcuMDQzOVpNMTcuMDQzOSA3Ni4yMjIxSDkuOTQ2NjlWODMuMzE5NEgxNy4wNDM5Vjc2LjIyMjFaTTE3LjA0MzkgNy42MTUzMkg0MC43MDRWLTYuNTc5MTlIMTcuMDQzOVY3LjYxNTMyWk0yNC4xNDEyIDc2LjIyMjFWMC41MTgwNjZIOS45NDY2OVY3Ni4yMjIxSDI0LjE0MTJaTTQwLjcwNCA2OS4xMjQ5SDE3LjA0MzlWODMuMzE5NEg0MC43MDRWNjkuMTI0OVpNNDIuNTgwNSA2OS4xMjQ5SDQwLjcwNFY4My4zMTk0SDQyLjU4MDVWNjkuMTI0OVpNNDcuODAxMyA2OS4xMjQ5SDQyLjU4MDVWODMuMzE5NEg0Ny44MDEzVjY5LjEyNDlaTTc4LjU1NiAzOC4zNzAxQzc4LjU1NiA1NS4zNTU1IDY0Ljc4NjcgNjkuMTI0OSA0Ny44MDEzIDY5LjEyNDlWODMuMzE5NEM3Mi42MjYxIDgzLjMxOTQgOTIuNzUwNSA2My4xOTQ5IDkyLjc1MDUgMzguMzcwMUg3OC41NTZaTTQ3LjgwMTMgNy42MTUzMkM2NC43ODY2IDcuNjE1MzIgNzguNTU2IDIxLjM4NDcgNzguNTU2IDM4LjM3MDFIOTIuNzUwNUM5Mi43NTA1IDEzLjU0NTMgNzIuNjI2IC02LjU3OTE5IDQ3LjgwMTMgLTYuNTc5MTlWNy42MTUzMlpNNDIuNTgwNSA3LjYxNTMySDQ3LjgwMTNWLTYuNTc5MTlINDIuNTgwNVY3LjYxNTMyWk00MC43MDQgNy42MTUzMkg0Mi41ODA1Vi02LjU3OTE5SDQwLjcwNFY3LjYxNTMyWiIgZmlsbD0iYmxhY2siIG1hc2s9InVybCgjZG9zdS1kLWN1dG91dCkiLz48cGF0aCBkPSJNNjguOTIxNSAzNi4wMTM1QzY4LjkyMTUgMzYuMDEzNSA2NS43MzY5IDQ5LjQ3MzggNTEuNDIzMSA0OS40NzM4QzM3LjEwOTMgNDkuNDczOCAzMi41Nzg3IDM3LjM1OTYgMzIuNTc4NyAzNi4wMTM1IiBzdHJva2U9ImJsYWNrIiBzdHJva2Utd2lkdGg9IjcuNjkxNjEiIHN0cm9rZS1saW5lY2FwPSJyb3VuZCIgc3Ryb2tlLWxpbmVqb2luPSJyb3VuZCIvPjxwYXRoIGQ9Ik0wLjM0ODYzMyA4NS40OTQ2QzAuMzQ4NjMzIDg1LjQ5NDYgMjkuNDg1NiA4NS44MzA5IDM0LjgwOSA4NS42OThDNDQuODMzNyA4NS40NDc3IDUxLjI4NzIgODQuNDAyIDU3LjUyNjkgNzguOTcyNEM2Mi44MTI5IDc0LjM3MjcgNzUuMTM0MiA1OS42ODM2IDc1LjEzNDIgNTkuNjgzNiIgc3Ryb2tlPSJibGFjayIgc3Ryb2tlLXdpZHRoPSI2LjE2NDgyIi8%2BPC9zdmc%2B)](https://github.dosu.com/Dokploy/templates?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=Dokploy%2Ftemplates) [![Share Dosu with your team](https://img.shields.io/badge/Share%20Dosu%20with%20your%20team-1f6feb?style=flat)](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=Dokploy%2Ftemplates)
Author
Owner

@xenstar commented on GitHub (Apr 8, 2026):

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.

<!-- gh-comment-id:4205513778 --> @xenstar commented on GitHub (Apr 8, 2026): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#3675