An Ansible role to install Girder.
Further documentation on provisioning can be found here.
Ubuntu 14.04/16.04 or CentOS 7.
| parameter | required | default | comments |
|---|---|---|---|
| girder_path | no | $HOME/girder | Path to download and build Girder in. |
| girder_repo | no | https://github.com/girder/girder.git | Git origin for fetching Girder. |
| girder_version | no | master | Git commit-ish for fetching Girder. |
| girder_python | no | ansible_python | Path to a specific Python to install and run Girder against. Requires girder_pip be specified. |
| girder_pip | no | pip2 | Path to a specific pip executable to install against, can't be specified with girder_virtualenv. |
| girder_virtualenv | no | none | Path to a Python virtual environment to install Girder in. |
| girder_clone | no | yes | Whether provisioning should clone Girder into girder_path. |
| girder_update | no | yes | Whether provisioning should fetch new versions via git. |
| girder_force | no | yes | Whether provisioning should discard modified files in the working directory. |
| girder_web | no | yes | Whether to build the Girder web client. |
| girder_always_build_assets | no | no | Whether to always rebuild client side assets (has no effect if girder_web is disabled). |
| girder_daemonize | no | yes | Whether to install the relevant service files (systemd or upstart). Disabling this can be useful inside of containers which might not have an init system. |
| girder_enabled | no | yes | Whether to enable the installed service (requires girder_daemonize). |
| girder_plugins | no | [] | List of paths to external plugins to install. |
| girder_web_extra_args | no | none | Any additional arguments to pass to girder build. |
| girder_user | no | $SSH_USER | The (already existing) user to run Girder under, this defaults to ansible_user_id which is typically the user Ansible is running under. |
| fact name | comments |
|---|---|
| girder_files_updated | Whether or not the files installed for Girder changed during provisioning. This can be useful for determining if client side assets need to be rebuilt. |
| girder_use_upstart | Whether Girder decided to use upstart as the init system. |
| girder_use_systemd | Whether Girder decided to use systemd as the init system. |
| girder_build_executable | The full path to the girder executable. |
Examples can be found here.