With locked-down machines, the learners already loose the opportunity to have a working environment on their laptop at the end of the workshop. At this point, the easiest I believe is to just setup Jupyterhub on a server and then use the embedded shell (Terminado) to teach bash and git, and then the Notebook for Python or R. So they only need a browser on the local machines.
On Mon, Mar 28, 2016 at 10:23 AM Matt Davis <[email protected]> wrote: > You'll definitely need to work with the IT staff at the lab. A VM isn't > useful if you can't install get VirtualBox installed, for example, and > you'll want the VM pre-loaded so you don't have an entire lab trying to > download hundreds of MB on the day of the workshop. On the other hand, many > pieces of software work fine installed by a non-admin and it may not be an > issue. I would see about getting touch with the lab IT staff and seeing > what they think of the SWC installation instructions. > > On Mon, Mar 28, 2016 at 9:44 AM Mike Smorul <[email protected]> wrote: > >> A VM is one option. We've run workshops (not SWC/DC) based on VM's that >> have been pretty successful. You end up w/ a lot fewer setup issues, but >> there's less take-away for students unless you run them through EC2 or >> similar where they can walk away w/ a working VM/image. >> >> If it's a locked down lab you're teaching in, most sites tend to have >> some procedure for getting new software installed. Your host may have a >> better idea about this. Be prepared to hand them a complete set of >> instructions for installation and more importantly a set of tests they can >> run locally to ensure everything is installed (ie, open r studio, run >> x,y,z, or open this software, click click click and you should see x,y,z) >> >> -----Original Message----- >> From: Discuss [mailto:[email protected]] On >> Behalf Of Adam Obeng >> Sent: Monday, March 28, 2016 12:31 PM >> To: [email protected] >> Subject: [Discuss] Workshop with locked-down machines >> >> Dear colleagues, >> >> >> A workshop next month is using machines on which the users don't have >> admin access. As far as I can tell, that means that if there are any >> installation issues that we can't anticipate, they'll be stuck. >> >> Do you have any experience of similar circumstances, or any advice on how >> to proceed in this situation? Use a VM, perhaps? >> >> >> Cheers, >> >> Adam >> >> _______________________________________________ >> Discuss mailing list >> [email protected] >> >> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >> >> _______________________________________________ >> Discuss mailing list >> [email protected] >> >> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >> > _______________________________________________ > Discuss mailing list > [email protected] > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
