add userskeys feature/controller which is usefull to manage user's API key through admin panel
modified method name 'api_keys' to 'admin_api_keys' for user vs userskeys controller
Allow LWR client to cache files when used with updated LWR servers. This synchronzies the LWR client to changeset LWR (f1feeb46845db15430b41af500af5544e73a8d38).
Allow LWR caching to be configured via environment variables for pre-job_conf.xml setups. Updates LWR client to LWR changesets: 2effb7f7b7ad.
Fix small bug related to lwr client caching thread count. Updates LWR client through LWR changeset abac180.
LWR client fixes for Python 3. Brings Galaxy client in line through LWR changeset 4ce6788.
In LWR client, retry certain calls to get around transient peer reset connection errors.

See the following LWR changeset for full information: https://bitbucket.org/jmchilton/lwr/commits/95ce1503d53562a2e46cdbeb35d5c5d9cb35278c.
Fix bug in LWR cleanup logic.
Update LWR client through LWR changeset 80f90e94f780b361a27ca70a8c8cff6b7add27ca.

In addition to small cleanups and bug fixes, this adds ability to disable file staging (for the most part) by adding default_file_action="none" to LWR destination. This is outlined in greater detail in the following LWR changeset:

https://bitbucket.org/jmchilton/lwr/commits/1f214688c0f02cbb7b85fc033b96daf61d56a309

Setting default_file_action="none" requires a newer LWR server (1f214688c0f02cbb7b85fc033b96daf61d56a309 or better), transferring LWR jobs should continue to work with an older or newer LWR server.
Document some additional LWR functionality in job_conf.xml.sample_advanced.
Fix bug (inability to correctly configure curl transport using new job_conf.xml syntax) I introduced in d9f874a.
Display also creation time on dataset info page.
Update the LWR client through LWR changeset 3602261cf9fced102dd019a0ce22cb25f9e656d1.

Introduces syntax allowing LWR client to assign various actions for staging files on a per path basis - 'transfer', 'copy', or leave untouched ('none'). For full details see this LWR changeset: https://bitbucket.org/jmchilton/lwr/commits/b9471d7c3ccb61d56f558e055c997ff53a38d540.
Update LWR client through LWR changeset 430d650ba49a.

These changes include small code cleanups and the ability to pass job submission parameters through from client to server. Specifically, if the remote LWR is configured using the DRMAA manager, the destination parameter "submit_native_specification" should be passed through and used on the server. In theory this should be able to be set from the job_conf.xml or via dynamic job destinations.
Make some attempt to deal with failed uploads while handling LWR caching.

Updates LWR client through changeset https://bitbucket.org/jmchilton/lwr/commits/54df64df1a00579ea51d91ef7215d2046e94304b.
In LWR, handle 'ok' datasets which do not corresponding to existing files (previous tool produced no output). Should Galaxy prevent these datasets/hdas to be 'ok'.

Updates LWR client through LWR changeset: 1cc5f35ecb8b.
galaxy/galaxy-central a bien été ajouté dans default
galaxy: table grid css style + removing unused imports
Merge in pull request #134.
Merge in pull request #211.