ChanServ changed the topic of #cinch to: The IRC Framework | http://groups.google.com/group/cinch-ruby/ | Latest version: Cinch 2.0.4 – Change log at http://bit.ly/14Q4s6Z – Migration guide at http://bit.ly/GO4qkW | This channel is being publicly logged at http://irclog.whitequark.org/cinch/
doxuanhu_ has quit [Remote host closed the connection]
doxuanhuy has joined #cinch
sleetdrop has joined #cinch
rickmasta has joined #cinch
doxuanhuy has quit [Remote host closed the connection]
sleetdrop has quit [Ping timeout: 252 seconds]
sleetdrop has joined #cinch
jhaals has joined #cinch
jhaals has quit [Quit: jhaals]
sleetdrop has quit [Quit: Computer has gone to sleep.]
sleetdrop has joined #cinch
jhaals has joined #cinch
framling has joined #cinch
<framling> Sorry if this is a noob question, but how are bots usually run? Called from /etc/rc.local?
<Netfeed> i built cinchize to be able to run basic bots easily as daemons, but you can always run them inside a screen or something like that
<framling> Well I've been running my little bot in screen, but my VPS seems to get restarted a lot and I'd like to have it start at boot, but I can't get it working by calling it in /etc/rc.local.
jhaals has quit [Ping timeout: 252 seconds]
jhaals has joined #cinch
<dominikh> step one would be to change to a more reliable hoster :-P as for running it at boot, you'll have to name sure that you're running it under the right user, and if using rvm, rbenv or similar that you run it in the right environment
<dominikh> framling
<dominikh> *make sure. writing on a phone is painful
jhaals has quit [Quit: jhaals]
rails__ is now known as evilNirvana
evilNirvana has quit [Changing host]
evilNirvana has joined #cinch
sleetdrop has quit [Quit: Textual IRC Client: www.textualapp.com]
jhaals has joined #cinch
postmodern has quit [Quit: Leaving]
jhaals has quit [Ping timeout: 252 seconds]
jhaals has joined #cinch
jcrawford has quit [Ping timeout: 264 seconds]
jcrawford has joined #cinch
jhaals has quit [Quit: jhaals]
jhaals has joined #cinch
bean__ has joined #cinch
jhaals has quit [Ping timeout: 276 seconds]
davidh_ has joined #cinch
sleetdrop has joined #cinch
sleetdrop has quit [Max SendQ exceeded]
sleetdrop has joined #cinch
sleetdrop has quit [Max SendQ exceeded]
sleetdrop has joined #cinch
sleetdrop has quit [Max SendQ exceeded]
sleetdrop has joined #cinch
davidh_ has left #cinch [#cinch]
sleetdrop has quit [Quit: Computer has gone to sleep.]
ex0a has joined #cinch
<ex0a> how do i access the bot configuration settings like the channel(s) it is in?
<dominikh> bot.channels ?
<ex0a> okay i wasn't sure if there was a different way to access it
<ex0a> not very familiar with ruby
bean__ has quit [Quit: Computer has gone to sleep.]
bean__ has joined #cinch
bean__ has quit [Max SendQ exceeded]
bean__ has joined #cinch
bean__ has quit [Max SendQ exceeded]
bean__ has joined #cinch
bean__ has quit [Max SendQ exceeded]
bean__ has joined #cinch
davidh_ has joined #cinch
<davidh_> quick question - is there any way to use bot.nick in a plugin match?
v0n has joined #cinch
<dominikh> if you use lambdas, yeah
postmodern has joined #cinch
<dominikh> match {|m| m is the message; m.bot.nick is the bot's nick; return either a string or a regexp that should be used for the actual match; }
<dominikh> eh, match lambda {...
<davidh_> thanks, got it working now
bean__ has quit [Quit: Computer has gone to sleep.]
davidh_ has quit [Quit: So long, and thanks for all the lambdas]
<dominikh> hah
bean__ has joined #cinch
jcrawford has quit [Ping timeout: 252 seconds]
jcrawford has joined #cinch
v0n has quit [Ping timeout: 256 seconds]
bean__ has quit [Quit: Computer has gone to sleep.]
bean__ has joined #cinch
bean__ has quit [Client Quit]
bean__ has joined #cinch
bean__ has quit [Client Quit]