But when deploying through Docker, the container may not have that file.
When that is the case, you can use the
CLOUDENV_BEARER_TOKEN environmental variable to store the API token instead.
There are many ways to configure environmental variables in Docker so if you do not like this way, you can pick any other, but the idea will be the same no matter which implementation you use.
First, generated a new API token in the CloudEnv dashboard for use in Docker.
$ docker-compose run -e CLOUDENV_BEARER_TOKEN=string-from-dashboard \ CLOUDENV_APP_SLUG=app-name \ CLOUDENV_APP_SECRET_KEY=encryption-key \ web python console.py
It is critical that the
.cloudenv-secret-key file in the home directory of your application (which you get by running
cloudenv init or from someone else on your team who has already run
cloudenv init) is still in the home directory of your application inside your Docker container. That secret key can not be put into an environmental variable and should also never be checked into any source code repository.
That file contains your encryption key and without it, your application can not decrypt the data received from CloudEnv’s servers.