Grunt option to install arbor vs tangelo logo
Will enable non-ansible logo setting (extension of #109).
This was somewhat removed in the transition to a Girder plugin. When the time comes I would like to piggyback off of girder/girder#1093 for this.
How about the idea of a separate playbook? The Flow playbook would run first to completion. A second play book which downloads the arbor static web apps and changes the logo and preloads the collections could be a second optional step run on the second playbook and changes the flow instance into an arbor instance. Is there such a capability in vagrant to allow alternate provisioning?
On Apr 20, 2016, at 3:18 PM, Dan LaManna [email protected] wrote:
This was somewhat removed in the transition to a Girder plugin. When the time comes I would like to piggyback off of girder/girder#1093 for this.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub