Edgars Beigarts

This might be fixed in #69

This should be fixed in #69

There is no `docker-args`hook anymore, instead there is `docker-args-deploy`, `docker-args-build`, `docker-args-run` ``` root@dokku:/var/lib/dokku/plugins/enabled/volume# ln -s docker-args docker-args-deploy root@dokku:/var/lib/dokku/plugins/enabled/volume# ln -s docker-args docker-args-run ```

@sbehrends i'm not having this issue (dokku 0.4.1, docker 1.8.2 aufs)

docker-args-build got my volumes wiped out, the herokuish build process does some weird cleaning after build process...

- Version of dokku you use: latest (0.4.14 - 0.7.2) - Non-core plugins you use: - mlomnicki/dokku-deploy-hooks - ribot/dokku-slack - ~~mak-it/dokku-volume (will switch to storage when available)~~ - dokku/dokku-postgres -...

@metaskills we will probably lower the `connect_timeout` for now, or skip using threads. At least `pg` doesn't block - https://gist.github.com/08c1b336952df04f0e4645f376d995dc ``` ruby 2.3.1 pg THR2: 2018-11-28 14:56:57 +0200 START THR1:...

@metaskills as I mentioned in the previous comment, other db gems do behave differently - they don't block other threads, but tinytds blocks other threads

The problem is here https://github.com/j-mcnally/capistrano-slack/blob/d806534fe96ab7f835dd007389d05a17e373024b/lib/capistrano/slack.rb#L73

This feature is not implemented in exchanger, but looks like StartTimeZone and EndTimeZone is the way to go. Maybe exchanger could in future set this automatically using tzinfo gem.