Peter wrote:
Hi all,
I'm trying to install Galaxy on CentOS, and doing things under my own user account the basics look fine (sh setup.sh work, sh run.sh works, and I can access the galaxy webpages on localhost).
I'm now trying to do this via a new Unix/Linux user account just for Galaxy, as recommended here:
http://bitbucket.org/galaxy/galaxy-central/wiki/Config/ProductionServer
For security I have deliberately setup a "galaxy" user with no home directory and with login disabled (based on the apache user):
sudo /usr/sbin/adduser -s /sbin/nologin -M -l -r -c "Galaxy" galaxy
I have downloaded Galaxy using hg, moved the directory to /opt/galaxy-dist and made the new galaxy user the owner of this folder and its contents. Then:
sudo -u galaxy sh setup.sh
That seems to work, next:
sudo -u galaxy sh run.sh
This fails as it tries to write to ~/.python-eggs (i.e. my home directory, the galaxy user doesn't have a home directory), so based on the error message's suggestion to set PYTHON_EGG_CACHE what I have tied is editing run.sh to include the following line near the start:
export PYTHON_EGG_CACHE="/opt/galaxy-dist/.python-eggs"
That seems to work, but is is a good idea? Do you instead recommend giving the galaxy account a home directory, and installing galaxy there? It would make setting environment variables simpler...
I haven't ever tried without a real home directory or shell, but I don't know of any reason you wouldn't be able to run like this if you're not using a cluster. Please let us know if you encounter any more issues. Thanks, --nate
Thanks,
Peter _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev