In galaxy.masthead.mako, from line 194, the following code appears: if app.config.use_remote_user: if app.config.remote_user_logout_href: menu_options.append( [ _('Logout'), app.config.remote_user_logout_href, "_top" ] ) else: menu_options.append( [ _('Preferences'), h.url_for( controller='/user', action='index', cntrller='user' ), "galaxy_main" ] ) menu_options.append( [ 'Custom Builds', h.url_for( controller='/user', action='dbkeys' ), "galaxy_main" ] ) logout_url = h.url_for( controller='/user', action='logout' ) menu_options.append( [ 'Logout', logout_url, "_top" ] ) menu_options.append( None ) Why are Custom Builds only enabled if you're *not* using remote_user ? Is this because they're related to user preferences (as per the code in lib/galaxy/webapps/galaxy/controllers/user.py)? And then a followup, if I have to add a build using either a FASTA file or a lenfile and editing the Galaxy install on the server, where do I need to make changes? Thanks, Peter
Why are Custom Builds only enabled if you're *not* using remote_user ? Is this because they're related to user preferences (as per the code in lib/galaxy/webapps/galaxy/controllers/user.py)?
This may be an artifact of a time when user preferences were immutable. Do Custom Builds and Preferences work on your set up using remote users?
And then a followup, if I have to add a build using either a FASTA file or a lenfile and editing the Galaxy install on the server, where do I need to make changes?
Unfortunately, It'll go in different places depending on your use. What are you looking to do with the build? Thanks, J.
participants (2)
-
Jeremy Goecks
-
Peter van Heusden