We put websockify on our shared filesystem where all of our other scientific applications are stored and created and Lmod module that OnDemand can use to easily load the correct paths. Another option if you don't have a shared file system might be to use syncfiles to push the directory out to the nodes after you've installed it locally on the management node.
Mike On 7/6/20, 11:22, "Lachlan Musicman" <data...@gmail.com> wrote: CAUTION: This email originated from outside of the Colorado School of Mines organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe. Hola, We are installing Open On Demand which has a requirement of websockify>0.8.0 which in turn has a python3 requirement. CentOS 7 (for eg) only packages an older version of python-websockify, so we need to deploy manually. IE python3 /path/to/websockify/setup.py install What's the recommended way to do this - do we create a software kit, or a postscript, or just push it out with xdsh and add some documentation to remind ourselves to update it when we update underlying python? Cheers L. _______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user