No description, website, or topics provided.
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Dockerfile fix Dockerfile Jul 6, 2018
Dockerfile.template fix typo Jun 18, 2018
Dockerfile.windows.template Update Dockerfile.windows.template Apr 19, 2019
Jenkinsfile Add Jenkinsfile Aug 15, 2017
README.md Update README.md Nov 12, 2018
common.bash bump version Jun 19, 2018
configBuilder.sh switch dloads to curl for redirects Feb 19, 2019

README.md

ShibbIdP_ConfigBuilder_Container

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 (best to use an empty directory).

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.

Once the files have been written to your directory, the container terminates and can be deleted.

You can run the container directly from the 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 -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.