cause I can't upgrade prod until I get this one working
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
I have the same issue on both 1.4.2 and 1.4.3 - Have you found a solution for this? Thanks.
Recommended threads
- Export, Import or Migration giving this ...
As you can see in yhe screenshot i am not able to export any data or export the data from tables. Also it is affecting the migration from appwrite to appwrite h...
- local (self-hosted) sites issues
setup: - `composer run installer:dev` issues - Getting error when visiting the site ```Synchronous function execution timed out. Use asynchronous execution in...
- I'm getting an error on the console "j?....
On my self hosted instance version 1.8.1 the console is giving me this error when trying to view the rows for a table I recently created. My application is read...