I have 2 projects in my organization. One is used as my staging environment and one is used as my prod environment.
When I initialize an Appwrite project, I get my appwrite.json with one level of data. Is there a way to configure it such that I can have more flexibility in what Appwrite is targeting?
For example, having a payload
"env":
{ "staging": {
"projectId": "12345",
"projectName": "App Staging"
},
"prod": {
"projectId": "12ABC",
"projectName": "App"
}
}
"default": "staging"
and having the ability to run CLI commands like this:
appwrite functions createDeployment <stuff> --profile staging
I'm not necessarily proposing the implemntation details. This is just referencing what AWS CLI does when you have multiple roles.
Is there something that exists that can handle this?
This sounds like a good feature request.
For now, I'd have multiple appwrite.json files and maybe use a symlink to switch between the two.
That's a great workaround. Thanks!
Isn’t a “profile switching” feature already planned? IIRC, it was more planned for server/user switching, but it could be extended to project switching?
Ya, there's a feature request for that
If your issue has been solved, you can mark this post as closed by adding “[SOLVED]” to the beginning of the title
[SOLVED] Are There Appwrite Profiles?
Recommended threads
- mcp-server-appwrite 0.4 fails on startup...
I’m trying to use `mcp-server-appwrite` against Appwrite Cloud and the server authenticates successfully, but fails during startup validation when probing `tabl...
- open runtime version lacks behind
open runtime version in appwrite CLI is v4 while the hosted runtimes use v5, this mismatch does not permit to debug locally functions using recent runtimes (li...
- The /storage web page is not working in ...
The /storage web page is not working in Appwrite. Server : FRA