Changeset 1270:167c1e9c9859 for README.txt
- Timestamp:
- 05/02/08 15:42:59 (8 months ago)
- Files:
-
- README.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
README.txt
r877 r1270 1 INTRO 2 ===== 1 GALAXY 2 ====== 3 http://g2.bx.psu.edu/ 3 4 4 This program requires python 2.4 or later. To check your python version type: 5 The latest information about Galaxy is always available via the Galaxy 6 website above. 5 7 6 python -V. 8 HOW TO START 9 ============ 10 Galaxy requires Python 2.4 or 2.5. To check your python version, run: 7 11 8 To start a server you need to do run the server as: 12 % python -V 13 Python 2.4.4 9 14 10 python universe.py 15 Before starting Galaxy for the first time, please run the setup script: 11 16 12 This will start a server on localhost port 8080. 13 In your browser go to: http://localhost:8080 and you should see the 14 Galaxy environment with some default tools. To customize the tools that 15 are loaded see tool.conf.sample To customize the way your server is ran edit 16 universe.conf 17 % sh setup.sh 17 18 18 *Note* certain tools may require certain libraries to be present. 19 (See run.sh for more details) 19 If setup.sh finishes successfully, you can then proceed to starting Galaxy: 20 20 21 % sh run.sh 21 22 22 RUNTIME ENVIRONMENT 23 =================== 23 Once Galaxy completes startup, you should be able to view Galaxy in your 24 browser at: 24 25 25 The default server home will be the directory where the program starts. 26 You can use the UNIVERSE_HOME environment variable to point to a different 27 server home. The path that the UNIVERSE_HOME variable points to must be 28 a directory with the following subdirectories: 26 http://localhost:8080 29 27 30 database 31 database/files 32 database/import 33 tools 28 You may wish to make changes from the default configuration. This can be done 29 in the universe_wsgi.ini file. Tools are configured in tool_conf.xml. Details 30 on adding tools can be found on the Galaxy website (linked above). 34 31 35 OPTIMIZED LIBRARIES 36 =================== 32 Not all dependencies are included for the tools provided in the sample 33 tool_conf.xml. A full list of external dependencies is available at: 37 34 38 To allow python to load optimized libraries the path to these must be listed 39 in the python path. See the previous section or run.sh for an example. Loading 40 the optimized Cheetah templating libraries can lead to significant 41 performance gains. 42 43 At startup you the log message: 44 45 Optimized Namemapper: True|False 46 47 will tell you whether the optimized Cheetah template was loaded (or not). 48 49 TOOL DEVELOPMENT 50 ================ 51 52 See the wiki pages for more details: 53 54 http://g2.bx.psu.edu 35 http://g2.trac.bx.psu.edu/wiki/ToolDependencies