Adrià Mercader

This looks good @Kyle-Falconer, I tested it and worked perfectly. Would you mind adding some documentation on `deployment.rst` about the option to use Docker? Also just because we don't have...

Sounds great, thanks @Kyle-Falconer

@jbrown-xentity is this issue happening with the latest version of DataPusher? [This](https://github.com/ckan/datapusher/issues/116#issuecomment-336491297) seems to suggest it might had been fixed when refactoring to use requests. If it's still an issue...

I don't think this is related to SSL. The first exception you get is a 403 error. This is caused when the datapusher extension [in CKAN core](https://github.com/ckan/ckan/blob/master/ckanext/datapusher/logic/action.py#L116:L146) tries to contact...

Yes, and it should follow the same naming convention as other similar config options like [`ckan.auth.login_view`](https://docs.ckan.org/en/latest/maintaining/configuration.html#ckan-auth-login-view), so it should be named `ckan.auth.route_after_login` (but support the old version of course)

I always lean towards trying to not break stuff, specially if the config option has been around for a while. We can show a deprecation message if the old variant...

Looks like we need to remove the `if 'size' not in resource` here? https://github.com/ckan/ckan/blob/97d48e1d5ad0c52ba7352baa155bb320c74f0ae6/ckan/logic/action/update.py#L305 Do you want to give it a go and submit a PR if it works @bzar...

Thanks @anotheredward, it's great that you want to work on this! AFAICT the current `ckan.auth.public_user_details` flag works at two levels, the full user list and the user details returned by...

@davidread yes sorry, fixed it now

@ipimpa I can not reproduce this in a CKAN 2.9.5 install and I'm a little confused about the details. In CKAN 2.9 there are two cookies set by default: *...