glaszig

with rails 7 on ruby 2.7 i'm using this patch to get around the issue: ```rb module DisableStarttls def build_smtp_session super.tap do |smtp| unless settings[:enable_starttls_auto] if smtp.respond_to?(:disable_starttls) smtp.disable_starttls end end...

@joshuaswilcox i was under that impression, too, but it somehow has no effect. i tried ``` plug :put_layout, {MyApp.LayoutView, "app.html"} ```

this hasn't been merged yet? rails 4.0 won't have `set_table_name` afaik.

it doesn't. at least anymore. on 10.2 with `pkg` version 1.9.4 ``` $ vagrant up btsync [...] TASK [JoergFiedler.freebsd-jail-host : Install additional packages] ************ failed: [btsync] (item=[u'tmux']) => {"failed": true,...

also, i had to do this to have `ansible-galaxy` not complain about roles missing from the central repo. ```diff diff --git a/roles.yml b/roles.yml index 985a920..59732de 100644 --- a/roles.yml +++ b/roles.yml...

it runs successfully on freebsd 11. but `vagrant up btsync` only creates 1 jail: ``` $ sudo iocage list JID UUID BOOT STATE TAG IP 1 b1d98d3d-f21c-11e6-a3e2-080027a82d61 on up syslogd.darkcity...

... because it seems to be running the jailed playbook with the same paramters multiple times when it should run with playbook-specific params. weird. ``` PLAY [btsync] ****************************************************************** TASK [setup]...

thanks. in my case the playbook still appears to run everything with only one (the first created) jail. am i doing something wrong? ``` $ ansible --version ansible 2.0.2.0 ```...

good lord! ansible is a bloody moving target. version < 2.1 won't work because it misses the `chroot` parameter which was only added in 2.1. then there's these weird bugs...

i wonder why this is not implemented using the callbacks. would be much cleaner, not clutter the base class with specifics. could also be released as a seperate gem.