On Thu, Sep 9, 2010 at 2:56 PM, Ry4an Brase <ry4an+galaxy@msi.umn.edu> wrote:
The initial work around I found online was to create a ~/.hgrc file containing the following:
[trusted] users = * groups = *
Just remove the users= line and change groups from '*' to 'galaxy_admin', and you have a fine solution. ... Creating a trust block in your ~/.hgrc was a fine solution, just tweak it to trust as narrowly as possible and you're good to go.
Understood. Of course, any other developers/admins here will have to do the same in their ~/.hgrc but that isn't a great hardship as long as I document it.
I would, however, recommend committing before doing the update. If you commit you know that no matter how poorly the update goes you can always 'hg update' back to exactly where you were. Whereas, if you 'pull -u' (pull with automatic update) there's no way for you to revert if you don't like what happened.
I will try that in future.
Given the advice from the other thread is to create the galaxy user account as a normal login account, do you normally run "hg pull" etc as the galaxy user?
I run them as me and then chmod the working dir files over, but only because I have our galaxy user set to have no login shell. Either works.
Oh good. Our administrator did not seem happy about making the galaxy user a login account - nice to know others are already using galaxy with a no login shell account. Thanks, Peter