Corin Langosch

Hmm yeah, maybe you are right. But afaik it just calls some command-line tool to generate the file, so most probably they won't be able to do anything about it...

I made some changes in the meanwhile: 1. The ruby version is now redetected after the repository has been checked out. This is important when new version of the application...

Sorry, but I don't see any warning? Instead it tells me that I don't have to do anything (which is wrong): This gem has been incorporated into Rails 3.2 which...

This bug is more or less a complete show stopper when using docker-compose :-1:

This bug is more or less a complete show stopper when using docker-compose :-1:

Still happening with current docker 20.10.18 :-1:

@pkieltyka Why not simply introduce an additional method `URLParamDecoded` which uses the proposed workaround?

Really looking forward to this feature too!

@0n1cOn3 What about using two vms in different availability zones/ datacenters, a floating/ virtual IP for headscale, and a local postgres master/ slave setup. Use keepalive to control the failover.

I tried using it without the `$el` and it does not work for me. Probably the proxy is broken? Failing code: ``` view = new MyApp.Views.SomeEdit(model: @model) modal = new...