4
Docker Compose env to secrets
Source: docmost/docmost#38 · opened by @Technetium1
From
> Don't use environment variables to pass sensitive information, such as passwords, in to your containers. Use [secrets]( instead.
This would require major reformatting and an update to the instructions, would it be good to do this before a stable release is tagged? Is it worth the effort to do it "correctly" in the first place?
---
DATABASE_URL shouldn't need password defined statically here when using env, but _probably_ needs to be altered if moving to secrets because secrets are instead mounted to /run/secrets/secretname
---
These env entries are also relevant:
> Don't use environment variables to pass sensitive information, such as passwords, in to your containers. Use [secrets]( instead.
This would require major reformatting and an update to the instructions, would it be good to do this before a stable release is tagged? Is it worth the effort to do it "correctly" in the first place?
---
DATABASE_URL shouldn't need password defined statically here when using env, but _probably_ needs to be altered if moving to secrets because secrets are instead mounted to /run/secrets/secretname
---
These env entries are also relevant:
No pledges yet. Be the first to back this.
Comments
Similar requests
docker: Use standard OCI labels to set the version
1 vote · 0 comments
[Feature Request] Allow docker process to run as different user
1 vote · 0 comments
[Feature Request] - Table with variable substitution
1 vote · 0 comments
HTML base64 images are not getting imported
0 votes · 0 comments
Access Logs
1 vote · 0 comments
No comments yet.