Hi,
Recently I followed the guide on http://bitbucket.org/galaxy/galaxy-central/wiki/Config/WebApplicationScaling. So I created two ini files, one for the web apps and 1 for the runner. Now is my question, what purpose does the universe_wsgi.ini serve. As I found out yesterday is that this ini is still used by the manage_db.sh script.. I never updated this universe_wgsi.ini file, although I moved to another database. So this script updated the wrong database.. error on my side I guess, but should I really keep 3 universe_wsgi files? And if so, what should be in which, as I now have most of the parameters in all three ini files..
Cheers,
Jelle
Jelle Scholtalbers wrote:
Hi,
Recently I followed the guide on http://bitbucket.org/galaxy/galaxy-central/wiki/Config/WebApplicationScaling . So I created two ini files, one for the web apps and 1 for the runner. Now is my question, what purpose does the universe_wsgi.ini serve. As I found out yesterday is that this ini is still used by the manage_db.sh script.. I never updated this universe_wgsi.ini file, although I moved to another database. So this script updated the wrong database.. error on my side I guess, but should I really keep 3 universe_wsgi files? And if so, what should be in which, as I now have most of the parameters in all three ini files..
Hi Jelle,
Unfortunately, you'll need to maintain at least the database connection string in universe_wsgi.ini, and it has to exist for the egg check/fetch code. It's not ideal but we haven't written a workaround yet. You could also just symlink universe_wsgi.ini to your webapp ini file.
--nate
Cheers,
Jelle
galaxy-user mailing list galaxy-user@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-user
galaxy-user@lists.galaxyproject.org
-
Jelle Scholtalbers -
Nate Coraor