Appwrite 1.4.2 Docker-Compose Fails to Start Executor

cause I can't upgrade prod until I get this one working

TL;DR

User is experiencing an issue with Appwrite 1.4.2 Docker-Compose failing to start executor. They are seeking a solution but no concrete solution is mentioned in the thread. Some suggestions are provided, such as comparing different versions of Appwrite and updating the Coolify template. The user also mentions the possibility of manually creating a new instance or using the Coolify template to set up a new distinct instance. They are also considering automating the Appwrite ENV to Coolify Template creation process. No definitive solution is provided in the thread.

Also Coolify is quite a good product.

How?

it's pretty cool tbh

Your color has just changed 😉

I use it for development purposes before I'm ready to switch to prod, I create new Appwrite test env's for them

ooh yay 🙂

like for instance right now

creating a 1.4.2 on Coolify to test migration and stuff

and to test the appwrite functions before switching my FastAPI servers to use Appwrite functions instead

cause GCC can now be built in with 1.4.2

I'm not sure, but I would imagine you could automate the Appwrite ENV -> Coolify Template creation pretty easily

cause you guys have all the docs and everything, I just need to think about how to do it realistically, in the meantime was hoping to get 1.4.2 up, if it's too annoying I can write the automation

You can look at the manual installation and see how to change it to set up a new distinct instance: https://appwrite.io/docs/self-hosting#manual

I think that Coolify uses temporary docker-compose file

I mean manually doing docker-compose up -d with a modified docker compose to make sure it creates a new instance

I can technically create one myself from GitHub

I'll work on a solution thank you guys I'll update soon

sort of related, is this an error in the docker-compose

Ah yes...we fixed 1.4.2 release but our website needs to be redeployed too

hey do you have a second today to go over the structure of Coolify vs Appwrite? They have Traefik set up in their containers automatically, and the exact structure is here: https://github.com/coollabsio/coolify-community-templates/blob/main/CONTRIBUTION.md but I could use some guidance on certain things

I don't think I'll have time.

I would recommend comparing 1.3.8 (https://github.com/appwrite/appwrite/blob/1.3.8/app/views/install/compose.phtml) and 1.4.2 (https://github.com/appwrite/appwrite/blob/1.4.2/app/views/install/compose.phtml)

and then see how the coolify template should be updated: https://github.com/coollabsio/coolify-community-templates/blob/main/services/templates/appwrite.yaml

I did, but tbh the hard part is trying to figure out the network/volumes, I'll keep messing with it

it looks like they set a custom prefix for it all:

https://github.com/coollabsio/coolify-community-templates/blob/83be1cded4b1762d62dcfef20cc11fb33f9f8ebb/services/templates/appwrite.yaml#L204C9-L204C21 vs https://github.com/appwrite/appwrite/blob/5717fbe28243a7616434d908554db51d28c4f35d/app/views/install/compose.phtml#L695