Timeline for How do you hide sensitive information held in variables on a docker-compose file
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2019 at 20:34 | comment | added | J86 |
Thanks, I figured it out. I was using var: value instead of var=value.
|
|
| Mar 29, 2019 at 20:33 | vote | accept | J86 | ||
| Mar 29, 2019 at 19:43 | comment | added | J86 | Thank you for the clarification @swysocki, I'm getting an issue about whitespace! I've updated the question. | |
| Mar 29, 2019 at 18:44 | comment | added | swysocki |
Yes, the host where you execute docker-compose up will need the .env file in the current working directory. Those variables must match the variables declared in your compose file.
|
|
| Mar 29, 2019 at 17:57 | comment | added | J86 |
Just to be clear, by host you mean the VPS where my sites are running? So in /var/www/html/mysite.co.uk/ I'll have a .env file with the JSON where the keys match the environmental variables that my application is expecting?
|
|
| Mar 29, 2019 at 17:28 | history | answered | swysocki | CC BY-SA 4.0 |