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
- Cannot migrate from Supabase
Hi, I was trying to migrate from Supabase to the Appwrite database. My database had around 190K columns. I tried it twice. Both times, after 2 days, the proce...
- Appwrite Remote MCP Server not working i...
Whenever I tried Authenticate - Appwrite Login in Browser - Paste Code, it always says `Error: calling "initialize": sending "initialize": Unauthorized` Already...
- "Invalid console fingerprint" when unpau...
I've tried logging out and logging back in, still can't figure out why this is happening.