Nate Coraor 3802816b69 User interface to permissions, and a bunch of changes to ensure that
both permitted_actions and groups are set appropriately on datasets.
Somewhat tested and mostly working, but needs more testing.

Greg: If a userless session has a history, if that user logs in,
the DefaultHistoryGroupAssociation for the current history as well
as the datasets in that history are supposed to be updated with the
permissions in DefaultUserGroupAssociation, but this isn't happening.
Possibly because the default permissions on userless histories create
datasets in the public group with only the DATASET_ACCESS permission
(or possibly for another reason).  What are the implications of giving
public users DATASET_MANAGE_PERMISSIONS?
2008-08-20 18:11:04 -04:00
2008-05-02 19:42:59 +00:00
2007-02-08 20:16:16 +00:00
2008-04-11 20:14:32 +00:00
2007-10-31 19:12:00 +00:00

GALAXY
======
http://g2.bx.psu.edu/

The latest information about Galaxy is always available via the Galaxy
website above.

HOW TO START
============
Galaxy requires Python 2.4 or 2.5. To check your python version, run:

% python -V
Python 2.4.4

Before starting Galaxy for the first time, please run the setup script:

% sh setup.sh

If setup.sh finishes successfully, you can then proceed to starting Galaxy:

% sh run.sh

Once Galaxy completes startup, you should be able to view Galaxy in your
browser at:

http://localhost:8080

You may wish to make changes from the default configuration.  This can be done
in the universe_wsgi.ini file.  Tools are configured in tool_conf.xml.  Details
on adding tools can be found on the Galaxy website (linked above).

Not all dependencies are included for the tools provided in the sample
tool_conf.xml.  A full list of external dependencies is available at:

http://g2.trac.bx.psu.edu/wiki/ToolDependencies
Languages
Python 66.5%
Vue 12.8%
TypeScript 11.3%
JavaScript 3.7%
Jupyter Notebook 2.7%
Other 2.8%