It is pretty simple — still, it might be worth me writing some documentation.
And too simple, for some: I see two folders there from non-UVM “contributors.” Apparently, I had the default permissions set such that “Everyone” could create folders. I have rescinded that permission, so you may want to try creating yet another new test folder, and then deleting it, just to be sure.
I’m trying to decide how best to manage this server in a sustainable, scalable fashion. Options:
o current method: use a single “admin” username and password (uvcmaps:spamcmvu), and hand that out to designated departmental coordinators to manage their own stuff
o create admin accounts (jbellum, jhenry, pbierman, etc.) for designated departmental coordinators to manage their own stuff
o Appoint a CMAP server czar (me or some TechCat or Account Services) who keeps a single “admin” username and password and creates folders for designated departmental coordinators to manage their own stuff
Current method is simplest, but has a small security concern in that too many people have super powers. If, say, designated departmental coordinator Pat Q Taireristt is fired and leaves UVM in a Huff, Pat could maliciously delete everyones folders unless we change the password and tell all the other designated departmental coordinators.
Creating admin accounts for all designated departmental coordinators allows us to delete Pat’s account, and everyone else is unaffected
But having either one shared or multiple personal accounts, all with root access to the UVM Public CMAP server, could create a “too many cooks” situation: should Academic Computing and the Center for Teaching and Learning each have folders at the top level, or should ACS and CTL have folders inside a top level folder called “Learning Resources?”
Thoughts? Does it really matter?
