
Are there any guides regarding deploying Swift functions to self hosted appwrite docker? Would be massively helpful.
The one I found is out of date https://dev.to/appwrite/create-and-run-welcome-email-appwrite-cloud-function-with-swift-2m1h

deploying to self-hosted vs cloud should be pretty much the same, so you'd follow the same docs: https://appwrite.io/docs/products/functions/deployment

I've tried with official doc a simple function results in error when deploying

what version of appwrite do you have?

1.4.9

What's your folder structure. How did you deploy and what are your function path and entrypoint settings?

I used manual deployment and uploaded code.tar.gz
as attachement, folder structure as screenshot. Also included settings on appwrite.

Comparing with our starter template: https://github.com/appwrite/templates/blob/main/swift/starter/Sources/index.swift
The only significant difference is nesting (folder phone
), and package name in Package.swift
. Can you please try to copy what we do in starter? Once we have your function up and running, we can better spot what exact change is causing this fail, and implement a proper fix

After I trying with the code in starter
the deployment is successful. However tried deploying again with the previous structure and it also succeeded

So we can mark this as solved now?

Yes

Heyo, please mark this as solved by adding [Solved] at the beginning of the title, thanks!

[SOLVED] Deploying swift function to self hosted environment
Recommended threads
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
