ur5us has quit [Remote host closed the connection]
ur5us has joined #jruby
PiaMuehlen has joined #jruby
PiaMuehlen has quit [Client Quit]
ur5us has quit [Ping timeout: 260 seconds]
nirvdrum has quit [Ping timeout: 240 seconds]
nirvdrum has joined #jruby
Antiarc has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
Antiarc has joined #jruby
subbu is now known as subbu|away
xardion has quit [Remote host closed the connection]
subbu|away is now known as subbu
xardion has joined #jruby
subbu is now known as subbu|brunch
subbu|brunch is now known as subbu
<fidothe>
is warbler still the recommended route for bundling/deploying a web app? I just got asked about a low-traffic REST service that needs a Java library and thought, oooh, I could do this in about 10 lines of Sinatra...
<fidothe>
@headius[m] Sorry about calling the test case method aMethod. Seemed simplest at the time and now seems dumb as rocks.
subbu is now known as subbu|away
subbu|away is now known as subbu
ur5us has joined #jruby
<headius[m]>
Not generally, no
<headius[m]>
Re warbler
<headius[m]>
We recommend warbler only if your only deployment option is a Java web application server or there's some other reason you want to bundle things up in a war file
<headius[m]>
The primary recommendation is to deploy with a standard Ruby server like puma if you are able, so your 10 line Sinatra app would be 👍
<headius[m]>
Of course all that said, if warbler is the easiest path to getting an app deployed, go for it
<headius[m]>
fidothe no worries on that method name, I'm just glad we have a clear test case that shows we need to make some adjustments. It will definitely be addressed for 9.3
<fidothe>
headius[m]: on the web app front, an executable .war sounds quite appealing for this particular use case, might try both ways. All my production stuff with JRuby has been non-web stuff
<headius[m]>
Sure that's a pretty slick way to go. I wonder if we should try to make Puma work from a jar file...the plumbing is all there already.