Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use environment variables for API KEY and PROJECT ID #14

Open
avinashupadhya99 opened this issue Oct 5, 2021 · 5 comments · May be fixed by #21
Open

Use environment variables for API KEY and PROJECT ID #14

avinashupadhya99 opened this issue Oct 5, 2021 · 5 comments · May be fixed by #21

Comments

@avinashupadhya99
Copy link

Using environment variables for API KEY and PROJECT ID makes it not secure but also makes it easy for people wanting to try out this project. There can be a .env.example file which has empty values for the environment variables. The person setting up the project can just cp .env.example .env and fill in the appropriate values.

@harshmathurx
Copy link

I think we should add an example.env file with empty values
I would like to help

@tejasborde
Copy link

@avinashupadhya99 can you please explain this issue.Like i have used the .env file in my projects. About .env.example can you explain in detail please ?

@avinashupadhya99
Copy link
Author

The .env.example file is an example .env file that would contain all the names of the environment variables necessary for .env. Here's an example -

APPWRITE_ENDPOINT=
APPWRITE_PROJECT_ID=
APPWRITE_API_KEY=

This is used as a reference to creating the .env since the .env file will not be commited to the repo.

@MSVelan
Copy link

MSVelan commented Oct 26, 2022

I would like to help out with this issue. Can you assign it to me?

@nikhilbuts
Copy link

@avinashupadhya99 Can you Please assign me this issue? I will do that.

@pandfun pandfun linked a pull request Oct 11, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants