Guest9014 has quit [Quit: Konversation terminated!]
Guest9014 has joined #ruby
Guest9014 has quit [Ping timeout: 256 seconds]
bluedust has joined #ruby
darkxploit has joined #ruby
taupiqueur has joined #ruby
gproto23 has quit [Quit: Leaving]
szkl has quit [Quit: Connection closed for inactivity]
taupiqueur has quit [Ping timeout: 240 seconds]
bluedust has quit [Read error: Connection reset by peer]
bluedust has joined #ruby
bluedust has quit [Ping timeout: 240 seconds]
bluedust has joined #ruby
pmwals09 has joined #ruby
pmwals09 has quit [Remote host closed the connection]
jlindgren_ is now known as jlindgren
bluedust has quit [Remote host closed the connection]
fef has joined #ruby
bluedust has joined #ruby
bluedust has quit [Ping timeout: 250 seconds]
bit4bit has joined #ruby
sunslider has joined #ruby
<sunslider>
hi guys, not ruby native here sorry:) I have Rack::Handler::WEBrick.run(app). how can I make it listen on another port?
<ox1eef>
sunslider:.run(app, Port: xxxx)
<sunslider>
works! thanks! @ox
<sunslider>
ox1eef ^_^
royo25 has quit [Quit: Bye]
<ox1eef>
+1
bit4bit has quit [Ping timeout: 250 seconds]
bit4bit has joined #ruby
szkl has joined #ruby
bit4bit has quit [Ping timeout: 256 seconds]
Aylat has joined #ruby
Aylat has left #ruby [#ruby]
oxfuxxx has quit [Quit: can you please adjust your IRC quit message to be less transphobic?]
bluedust has joined #ruby
symb0l has joined #ruby
gr33n7007h has joined #ruby
Aylat has joined #ruby
Aylat has quit [Client Quit]
Aylat has joined #ruby
TomyWork has quit [Remote host closed the connection]
<Vaevictus>
ox1eef: responses that quick and accurate, makes me wish my timestamps had seconds on them. good job
<symb0l>
Is there a good way to namespace functions, without using a class? I don't want to do a SomeObject.new(a,b,c).do_something() but I also don't want do_something() to pollute global namespace
Aylat has quit [Read error: Connection reset by peer]
<symb0l>
Just seem unneeded to have to initialize an object for that
<kenichi>
symb0l: check out Module.module_function
<symb0l>
kenichi: appreciate it.
fef has quit [Remote host closed the connection]
Hess has quit [Quit: Ping timeout (120 seconds)]
Hess has joined #ruby
fef has joined #ruby
<adam12>
symb0l: Alternatively, define methods on self inside a module. It's similar to module_function, but with some differences.
<ox1eef>
'module Foo; def bar; end; extend self; end' is another option.
<adam12>
I think that's similar to module_function, tho it probably doesn't copy the method like IIRC module_function does.
<adam12>
I wonder how many copies of the method `bar` exist when you extend self...
<ox1eef>
another difference is that module_function marks the instance methods below it as a private, and i dont believe 'extend self' alters visibility. usually id use module_function.
fef has quit [Remote host closed the connection]
bluedust has quit [Remote host closed the connection]
<symb0l>
Thanks, yeah, we haven't really made a ton of use of modules yet so lacking on what all the provide. but they look like exactly what we need
fdan has joined #ruby
legit has quit [Quit: reboot]
legit has joined #ruby
<leftylink>
pandabot: WHAT'S RUBY FLAGS
<pandabot>
rubyflags is: ruby -ple '$_.upcase!' < input.txt; ruby -nle 'BEGIN { i = c = 0 }; c += $_.size; puts "#{i += 1} #$_"; END { p c }' < input.txt
<leftylink>
oops, sorry for all caps
taupiqueur has joined #ruby
oxfuxxx has joined #ruby
oxfuxxx has quit [Ping timeout: 250 seconds]
taupiqueur has quit [Ping timeout: 256 seconds]
gproto23 has joined #ruby
fdan has quit [Ping timeout: 256 seconds]
taupiqueur has joined #ruby
oxfuxxx has joined #ruby
<adam12>
I don't think I've used capslock in 20 years
<IsoLinCHiP>
So I just found the gem minion, which makes scheduling jobs over rabbitmq quite comfortable. Sadly Im about 10 years to late and its not maintained anymore. https://github.com/orionz/minion#label-Chaining+multiple+steps . Can anyone recommend a similarly simple one?
<ox1eef>
i seem to remember one of the original travis ci crew working on libraries for rabbitmq. many years ago.
taupiqueur has joined #ruby
bluedust has joined #ruby
taupiqueur has quit [Ping timeout: 240 seconds]
bluedust has quit [Ping timeout: 250 seconds]
gproto23 has quit [Ping timeout: 250 seconds]
Guest9014 has joined #ruby
sunslider has quit [Quit: Client closed]
duds- has joined #ruby
taupiqueur has joined #ruby
oxfuxxx has joined #ruby
taupiqueur has quit [Ping timeout: 240 seconds]
<IsoLinCHiP>
adam12: RabbitMQ was a bonus, as I wouldnt need to setup an additional service, but featurewise most based on reddis seem to be more featureful
<IsoLinCHiP>
funny conincidance, I found the reference to minion on a blog by an adam :) 'tornado of razorblades'
symb0l has quit [Read error: Connection reset by peer]
graywolf has joined #ruby
symb0l has joined #ruby
va5c0 has quit [Quit: WeeChat 3.4]
va5c0 has joined #ruby
va5c0 has quit [Client Quit]
ua__ has quit [Ping timeout: 240 seconds]
va5c0 has joined #ruby
taupiqueur has joined #ruby
va5c0 has quit [Client Quit]
taupiqueur has quit [Ping timeout: 250 seconds]
<adam12>
IsoLinCHiP: Sidekiq is kind of defacto. I use Que if I'm using postgres generally, or SuckerPunch if I'm feeling especially crafty.
va5c0 has joined #ruby
va5c0 has quit [Client Quit]
va5c0 has joined #ruby
<havenwood>
adam12: Heh, I've used SuckerPunch too when it's viable and I'm feeling lazy.
va5c0 has quit [Client Quit]
va5c0 has joined #ruby
<havenwood>
Reboot? Prepare the data ion cannon!
<adam12>
havenwood: Both of them allow me to skip redis. I have nothing against redis, but everyone reaches for it way too early.
<adam12>
Que just had it's 1.0 release yesterday, and its' quite nice! I love me a pg based queue.
<adam12>
bbl.
<havenwood>
adam12: Yeah, I've gone the pg-backed queue route too a long time back. Unsure if it was que.
<havenwood>
Worked!
<havenwood>
Also stored files across partitions in pg.
<havenwood>
Postgres everything!
<havenwood>
What's the file store? PG. Queue? PG. Database? MySQL.
<havenwood>
I mean, PG.
<weaksauce>
was the db ever the bottleneck?
<havenwood>
weaksauce: I don't recall it ever being an urgent issue but we did move away from both as we started optimizing actual DB queries.
<havenwood>
weaksauce: I think the file storage bit was actually moving towards unworkable in the long run but I don't think queues were ever actually a problem.
<havenwood>
Like seven years ago, so memory failing me.
<weaksauce>
i see
Rounin has quit [Ping timeout: 256 seconds]
<havenwood>
Basically both worked for the entirety of development and swapped out to S3 and Redis at some point, probably not due to necessity.
<havenwood>
The file storage for uploads *seemed* jankier.