-
Notifications
You must be signed in to change notification settings - Fork 21
Test external database #141
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
Conversation
ef3d1e3 to
766b80f
Compare
|
I updated this for now to be based off the other prototype (#143) that includes development CLI, that allows building in this deployment, e.g. Where the last command will configure a |
766b80f to
a86546d
Compare
a86546d to
184a7c7
Compare
0f102a9 to
57acf22
Compare
|
This is passing now! This includes a commit that re-works how the |
accd6f5 to
8b1dc76
Compare
|
Added documentation |
3d2d8b1 to
155e0d0
Compare
0635182 to
6e21655
Compare
|
This includes #326 since the database checks fail for foreman-proxy setup (which doesn't require a database). |
6e21655 to
9c73b92
Compare
|
I split out one of the commits as it would be useful beyond this -- #346 |
9c73b92 to
0793e5e
Compare
f85528a to
0ff351e
Compare
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
0ff351e to
ca4a53f
Compare
This is using Vagrant to provide a way to do external database testing. There is a command dedicated to setting up an external database in the development CLI. I am starting with a separate job focused on just testing the external database.