Hi Ray, You will absolutely need command line access to the Galaxy server for some of the administration tasks - the web admin controls and web report tool only let you do some of the likely tasks. During the initial setup admin (sudo) rights would be useful, at very least you'll need the sys admin to help with mounting shared network drives, cluster integration, database setup. If you want to run cluster jobs as the associated Unix account of each user, or anything like LDAP logins, then again you will need help from your sys admin. See also: https://wiki.galaxyproject.org/Community/GalaxyAdmins Peter On Tue, Sep 22, 2015 at 9:07 AM, Raymond Wan <rwan.work@gmail.com> wrote:
Dear all,
I'm still new to Galaxy but was wondering if someone could offer some advice.
On a local Galaxy instance, if I were the Galaxy administrator but do not have sudo access on the machine itself, is this a problem? Or are the two roles intricately linked so that the Galaxy administrator will have to pester the system administrator frequently? The web interface alone is not sufficient for the Galaxy administrator.
(i.e., does a Galaxy administrator need sudo access ... or even just group access to the Galaxy subdirectory to effectively do his/her job? ...I mean making Galaxy owned by a Unix group and putting the Galaxy administrator in that group.)
As an aside, I was trying to do some alignment with bwa and realized I needed to prepare the genome by creating the index and an accompanying .loc file. The instructions [1] seem to imply some kind of command-line access..
Thank you for your help!
Ray
[1] https://wiki.galaxyproject.org/Admin/DataPreparation ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/