Back
Exposing project id and endpoint on GitHub
Is it best practice to expose your project id and endpoint in your appwrite.js file when publishing an NextJS or Angular project. If you use a .env file, that is not pushed to the repo, to store your project id and endpoint will the project still work when published.
TL;DR
Developers are discussing whether it is a good practice to expose project id and endpoint in appwrite.js file on GitHub for NextJS or Angular projects. Storing sensitive information in a .env file and not pushing it to the repo is recommended for security reasons. This method ensures the project will still work when published.