Change environment variables strategy

README.md

@@ -30,14 +30,14 @@ First of all you have to start the Docker container.
 
 The container is now running. Now you have to setup the Appwrite structure, but no worries I made a setup script.
 
-To start the script run `docker-compose exec pingvin-share node scripts/setup.js`.
+To run the script run `docker-compose exec pingvin-share node scripts/setup.js`.
 
 You're almost done, now you have to change your environment variables that they fit to your setup.
 
 1.  Go to your Appwrite console, visit "API Keys" and copy the "Functions API Key" secret to your clipboard.
 2.  Paste the key to the `APPWRITE_FUNCTION_API_KEY` variable in the `.env` file
-3.  Change `NEXT_PUBLIC_APPWRITE_HOST` in the `.env` file to the host where your Appwrite instance runs
-4.  Change `NEXT_PUBLIC_MAX_FILE_SIZE` in the `.env` file to the max file size limit you want
+3.  Change `PUBLIC_APPWRITE_HOST` in the `.env` file to the host where your Appwrite instance runs
+4.  Change `PUBLIC_MAX_FILE_SIZE` in the `.env` file to the max file size limit you want
 
 ## Known issues / Limitations
 
@@ -45,7 +45,6 @@ Pingvin Share is currently in beta and there are issues and limitations that sho
 
 - `DownloadAll` generates the zip file on the client side. This takes alot of time. Because of that I temporarily limited this function to maximal 150 MB.
 - If a user knows the share id, he can list and download the files directly from the Appwrite API even if the share is secured by a password or a visitor limit.
-- Because NextJS injects environments variables at build time, the website must be rebuilt when an environment variable changes. At the moment the container rebuilts the website after every restart. This takes some time.
 
 ## Contribute