Hi Peter, All of the tool-shed related required files will be automatically generated from the samples when you start your tool shed server as of change set 8708:2a34f751c32c. In the past, all of these same files were created if you started your Galaxy server using run.sh. It's no excuse, but that's why it slipped by me until now.
Thanks for alerting me to this issue! Greg Von Kuster On Jan 31, 2013, at 9:40 AM, Peter Cock wrote: > The following cryptic error is not helpful: > > $ sh run_community.sh > Command 'serve' not known (you may need to run setup.py egg_info) > No commands registered. > Have you installed Paste Script? > (try running python setup.py develop) > > I then noticed that there was no community_wsgi.ini file, and tried > using a copy of the sample: > > $ cp community_wsgi.ini.sample community_wsgi.ini > $ sh run_community.sh > (runs with no output, finished in 3s) > > Does it make sense to generate community_wsgi.ini automatically? > Or give an explicit error if it is missing? > > ___________________________________________________________ > 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: > > http://lists.bx.psu.edu/ ___________________________________________________________ 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: http://lists.bx.psu.edu/
