DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

How to restart droplet with new appwrite .env variables

Hi, I made some changes via the console/terminal ui to my appwrite .env file. But when I go back and check my console the changes i made aren’t reflected. Even after i restarted my droplet. How can I mitigate this? Thanks in advance.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Sign up now

Bobby Iliev • August 21, 2021

Hello,

According to the official Appwrite documentation, after editing your docker-compose.yml or .env files, you will need to restart your Appwrite stack by running the following compose command in your terminal:

docker-compose up -d

Hope that this helps. Regards, Bobby

Try DigitalOcean for free

Click below to sign up and get $100 of credit to try our products over 60 days!

Sign up