From f8ca077dc5c3f47f2684555c8160dca345e42377 Mon Sep 17 00:00:00 2001 From: Paul Caskey Date: Mon, 12 Nov 2018 06:56:57 -0600 Subject: [PATCH] Update README.md --- README.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index c923a78..440739d 100644 --- a/README.md +++ b/README.md @@ -8,15 +8,12 @@ The result is a set of files and directories containing everything needed to bui Once the files have been written to your directory, the container terminates and can be deleted. -Build this container like this: -docker build -t tierconfigbuilder . - -Run the container like this: -docker run --interactive --tty -v $PWD:/output -e "BUILD_ENV=LINUX" tier/shibbidp_configbuilder_container +You can run the container directly from teh docker hub like this: +docker run -it -v $PWD:/output -e "BUILD_ENV=LINUX" tier/shibbidp_configbuilder_container -OR, for a Windows container, like this- -docker run --interactive --tty -v $PWD:/output -e "BUILD_ENV=WINDOWS" tier/shibbidp_configbuilder_container +docker run -it -v $PWD:/output -e "BUILD_ENV=WINDOWS" tier/shibbidp_configbuilder_container After answering the questions in the configBuilder, your config will be written to several files and directories in the directory you mounted in the 'docker run' command above. The output defaults to placing certain IdP config files into a 'SECRETS' folder at the root to a) remove them from the rest of the config files so that b) the remaining config files can be easily burned into the container.