You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please implement a way for the management console to reflect the location where Appwrite was installed into by the docker commands. Better yet, it would be ideal, if the user could modify the env variables from within the management console itself, so they won't ever need to directly access the .env file.
🎤 Pitch
If the user forgets the location where they initialized Appwrite into, there is no way for them to easily access the .env file to configure Appwrite, unless they use some obscure docker commands which the majority of devs have no clue about. The user should not plow through pages of documentation to help them find out where they installed Appwrite nor how could they modify the environment variables.
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
Please implement a way for the management console to reflect the location where Appwrite was installed into by the docker commands. Better yet, it would be ideal, if the user could modify the env variables from within the management console itself, so they won't ever need to directly access the .env file.
🎤 Pitch
If the user forgets the location where they initialized Appwrite into, there is no way for them to easily access the .env file to configure Appwrite, unless they use some obscure docker commands which the majority of devs have no clue about. The user should not plow through pages of documentation to help them find out where they installed Appwrite nor how could they modify the environment variables.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: