Open source porject database credentials

[jacobcoro]

How could we hide/store the database login and password if our API server will be open source?

[StephenBrown2]

All the config settings are managed via environment variables and loaded via docker config in the particular .env file, so you would only need to add that file to .gitignore to not track changes such as adding credentials.

[alexmitelman]

Probably, it would be nice to have those files in .gitignore by default.
Users can commit all the changes right after running cookiecutter.

Also, cookiecutter-config-file.yml contains credentials in plain text. Maybe hide it as well?

[alexmitelman]

There are two solutions I can see here:

• naive: just edit .gitignore to add those files here (this will affect this repo as well)
• create a post-generate hook that will add those files to .gitignore to a newly generated project.

I can jump on the implementation, just wanted to discuss it here first.

[StephenBrown2]

post-generate would probably be best, since if you edit https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/master/%7B%7Bcookiecutter.project_slug%7D%7D/.gitignore it would affect all subdirectories in this repo as well, like you said.

[tiangolo]

Yeah, it depends on each use case, if you need to hide those secrets, like in a public repo, you can add the credentials as env vars. But you have to make sure they are available in your CI for testing, in your deployment CI or infrastructure, etc.

If you use a private repo and deploy to your private cloud, then it's not a problem to have them there.

That's why I don't enforce any git behavior with those files, but you are free to add them to .gitignore.

[github-actions]

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.