Vasiliy Kulikov opened 1 year ago
|
|||||||
Robin Shen changed fields 1 year ago
|
|||||||
This is not possible currently. I converted this as an improvement request. |
|||||||
Ok, I'll wait for an update of the improvement. Should I close this issue? |
|||||||
Just keep it open. Will be closed automatically when relevant code commits in. |
|||||||
Thank you. |
|||||||
OneDev changed state to 'Closed' 12 months ago
|
|||||||
State changed as code fixing the issue is committed (54aa4d65) |
|||||||
OneDev changed state to 'Released' 12 months ago
|
|||||||
State changed as build #3638 is successful |
|||||||
Check this for environment variables to store password in file: https://docs.onedev.io/installation-guide/run-as-docker-container |
|||||||
I've already tested it. It works => I'm happy. Only I haven't tested yet on restoring from backup, but I hope everything will be fine there. You are making improvements so fast... I'm impressed. Thank you! 👍 |
Type |
Improvement
|
Priority |
Normal
|
Assignee |
I am using Docker Compose to deploy OneDev with an external database (MariadDB). And I'm trying to hide sensitive data with Docker Secrets. For MariaDB, I use "MARIADB_ROOT_PASSWORD_FILE" and "MARIADB_PASSWORD_FILE" instead of "MARIADB_ROOT_PASSWORD" and "MARIADB_PASSWORD" respectively. This works, but I can't find a way to insert "/run/secrets/secret" in "hibernate_connection_password" and "initial_password" in OneDev's environment section in docker-compose.yaml. Is it possible? Or is there another way not to use sensitive data in docker-compose.yaml?