Use Secrets in your Project

Source

Once you’ve added members, secrets and files, you might want to use all of those in your project. To do so, before starting your project, run:

eval "$(ks source)"

It will load all secrets as environment variables, and move all files to the right place.

To improve your development experience, you could add this line to your starting scripts (package.json scripts, Makefile, etc.)

Use with a local .env file

In a development environment, you sometimes want to change a secret, or environment variable to a value private to you (e.g.: a TCP listening port, for instance).

To do so you can create a .env file at the root of the project, and its content will override the secrets managed by keystone.

Edit this page on GitHub