Update README.md

README.md

@@ -1,13 +1,23 @@
 # ShibbIdP_ConfigBuilder_Container
 
-This container runs the configBuilder script and generates a Shibb IdP config for TIER releases.
+This container runs the configBuilder script and generates a Dockerfile (and related dependencies) along with a default TIER Shibboleth IdP config, customized based on the user's reponse to a few questions.
 
-The config is written to /output in the container, which users should bind-mount to a directory of their choosing.
+The config is written to /output in the container, which users should bind-mount to a directory of their choosing (best to use an empty directory).
 
-The result is a zipfile with a Shibb IdP/Tomcat config.
+The result is a set of files and directories containing everything needed to build a TIER Shibboleth IdP container.  This includes the Dockerfile and related dependencies, along with the default TIER IdP config.
 
-Build this container like this: docker build -t tierconfigbuilder .
+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
+
+-OR, for a Windows container, like this-
+
+docker run --interactive --tty -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.
 
-Run the container like this: docker run --interactive --tty -v $PWD:/output -e "BUILD_ENV=LINUX" tier/shibbidp_configbuilder_container
 
-After answering the questions in the configBuilder, your config will be a zipfile in a child directory of the current directory named 'myconfigs' and should work on either a Linux or a Windows release.