-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move mysql creds to compose env variables #76
move mysql creds to compose env variables #76
Conversation
@@ -13,6 +13,6 @@ | |||
}, | |||
"storage": { | |||
"backend": "mysql", | |||
"db_url": "dockercondemo:dockercondemo@tcp(notarymysql:3306)/dockercondemo" | |||
"db_url": "gordontheturtle:dockerrulez@tcp(notarymysql:3306)/development" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this line be referencing DB_USER et al?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i believe this is the right format user:password@
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The format is fine, but the value are hard-coded. What I mean was the connection string should reference the env variables like : "${DB_USER}:${DB_PASS}@"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will that work w cobra we whatever lib you use I'm not familiar
On Jul 17, 2015, at 11:59, Richard Scothern notifications@github.com wrote:
In cmd/notary-server/config.json:
@@ -13,6 +13,6 @@
},
"storage": {
"backend": "mysql",
"db_url": "dockercondemo:dockercondemo@tcp(notarymysql:3306)/dockercondemo"
The format is fine, but the value are hard-coded. What I mean was the connection string should reference the env variables like : "${DB_USER}:${DB_PASS}@""db_url": "gordontheturtle:dockerrulez@tcp(notarymysql:3306)/development"
—
Reply to this email directly or view it on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, this should reference the env variables, and they should be setup before this container runs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does that work w cobra
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ive never used that lib lol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea what Cobra is :)
This thing will be deployed with Ansible, until infra switches to docker-compose, so changes to this file are for now immaterial
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oooooo i see, but in the container i see this being a problem maybe...
On Fri, Jul 17, 2015 at 1:06 PM, Richard Scothern notifications@github.com
wrote:
In cmd/notary-server/config.json
#76 (comment):@@ -13,6 +13,6 @@
},
"storage": {
"backend": "mysql",
"db_url": "dockercondemo:dockercondemo@tcp(notarymysql:3306)/dockercondemo"
"db_url": "gordontheturtle:dockerrulez@tcp(notarymysql:3306)/development"
I have no idea what Cobra is :)
This thing will be deployed with Ansible, until infra switches to
docker-compose, so changes to this file are for now immaterial—
Reply to this email directly or view it on GitHub
https://github.com/docker/notary/pull/76/files#r34926147.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok ya i think it works
cd58c9f
to
3234fed
Compare
hi! |
ping @endophage |
@thaJeztah the irony is not lost on us :) The major difference is between doing it/condoning it for everyone using docker. |
@diogomonica I know, sorry, couldn't contain myself 😄 (change LGTM) |
@RichardScothern Aaron is using a different compose file to deploy (he builds his own images from those we push to hub and deploys those). We want the files as they exist in the repo to be runnable locally so contributors can get up and running easily. With that in mind, we probably need to revert the changes for ansible. |
@endophage I'm aware of this :) What do you want to do with this PR? 🍰 |
@RichardScothern you personally, nothing, just addressing your earlier comments. |
so can i go back to what i had here originally ;) #76 (diff) |
3234fed
to
610a64c
Compare
updated |
@@ -12,6 +12,6 @@ | |||
}, | |||
"storage": { | |||
"backend": "mysql", | |||
"db_url": "dockercondemo:dockercondemo@tcp(notarymysql:3306)/dockercondemo" | |||
"db_url": "gordontheturtle:dockerrulez@tcp(notarymysql:3306)/development" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation looks off here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
having a rough day over here haha
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol
On Tue, Jul 28, 2015 at 4:17 PM, Sebastiaan van Stijn <
notifications@github.com> wrote:
In cmd/notary-server/config.json
#76 (comment):@@ -12,6 +12,6 @@
},
"storage": {
"backend": "mysql",
"db_url": "dockercondemo:dockercondemo@tcp(notarymysql:3306)/dockercondemo"
"db_url": "gordontheturtle:dockerrulez@tcp(notarymysql:3306)/development"
Indentation looks off here
—
Reply to this email directly or view it on GitHub
https://github.com/docker/notary/pull/76/files#r35713308.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw, no worries 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
retabbed the whole thing, it was def mixed tabs and spaces :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx, looks good now!
610a64c
to
17ef432
Compare
does docker-compose up work with this config? (as in, are we able to point notary to it and it works?) |
yessir |
but you may want to verify for yourself |
Signed-off-by: Jessica Frazelle <princess@docker.com>
17ef432
to
554ea0e
Compare
rebased.. |
come on people |
Now that I've been playing with Ansible, there's basically no difference in whether we include the variables in a config file or as ENV variables, they will get defined in the same place then the |
@jfrazelle going to close this as it'll be superceded by this PR #185 That PR will allow trust to take full control over deployments once I finish the integration. |
client: Add optional custom User-Agent to HTTPRemoteStore
closes #75