In my function i want to access the _APP_ENV environment variable, but i think this changed in the new update. For my workflow it doesn't really work having to manually create this variable in the appwrite console, since im switching between production(on server) to development(local pc) appwrite environments.
For now i'm gonna update the variables manually using the CLI when importing production. But would be nice not having to do that.
y'no there are project level variables now. maybe you can set the variables in your project instead of function?
or you can set the variable in the console and then don't overwrite the variables on deploy
Yeaa, i just thought you could access the appwrite variables in the local .env directly in the functions. But ill make use of the CLI, and think itll be fine.
[CLOSED] How to access .env variables in functions 1.4.2?
[SOLVED] How to access .env variables in functions 1.4.2?
Recommended threads
- Timed out waiting for runtime error
execution id 6a3e0791978712d81ee0 im having issue with appwrite function runtime performance. even after 4gbram and cpu same function sometimes completes in a...
- Function crash first run after a while
Big issue I’m facing , almost all functions crash or run for a very long time the first time i run them after a long time without running them I have a “help-c...
- Function global variables
when i create a top-level global variable in go or bun how will it behave? is the heap getting renewed on every execution or could i do some kind of temp. cachi...