xargoon has quit [Read error: Operation timed out]
xargoon has joined #rom-rb
snusnu has joined #rom-rb
postmodern has quit [Quit: Leaving]
cored has joined #rom-rb
cored has joined #rom-rb
cored has quit [Changing host]
xargoon has quit [Ping timeout: 260 seconds]
xargoon has joined #rom-rb
<solnic>
snusnu: cool!
jfredett has joined #rom-rb
jfredett1 has joined #rom-rb
jfredett has quit [Read error: Connection reset by peer]
jfredett has joined #rom-rb
mbj has joined #rom-rb
jfredett1 has quit [Ping timeout: 246 seconds]
knowtheory has joined #rom-rb
dkubb has joined #rom-rb
<dkubb>
good morning
<solnic>
dkubb: morning
<mbj>
dkubb: morning
mbj has quit [Quit: leaving]
<kalleth>
dkubb: morning
<dkubb>
sorry I haven't been around recently
<dkubb>
things kind of blew up at work the last week
<dkubb>
a client we've been bugging forever to upgrade their system (that we inherited) had an intrusion attempt, and we found lots of security holes and insecure data
<solnic>
dkubb: inorite ;)
<dkubb>
on the plus side I got to rebuild the system cleanly
<dkubb>
and I am really loving saltstack atm
<dkubb>
saltstack + vagrant + aws is a really nice combo. you can now easily deploy to aws from within vagrant
<dkubb>
I don't know if I'd use it for a huge system, but for a smaller one it works great
<mbj>
solnic: we are not listed on the eurucamp schedule!
<mbj>
solnic: So we have to ping them and prepare something :D
<mbj>
snusnu: ping
<mbj>
We still plan to give our "rom-style" workshop?
<snusnu>
mbj: yo
<mbj>
snusnu: have to run
<mbj>
snusnu: online later
<snusnu>
ok
mbj has quit [Quit: leaving]
snusnu has quit [Quit: Leaving.]
snusnu has joined #rom-rb
mbj has joined #rom-rb
<mbj>
hola
jfredett has quit [Quit: Leaving.]
<onewheelskyward>
como estas?
cobbr2 has joined #rom-rb
postmodern has joined #rom-rb
<mbj>
onewheelskyward: hehe, I only can say "hola", sorry :D
<onewheelskyward>
haha
<onewheelskyward>
no problemo.
<mbj>
como estas? Mui bien.
<mbj>
The only thing I remember from classes :D
<onewheelskyward>
For me it's that an un cerveza por favor.
<snusnu>
mbj: yo
<snusnu>
mbj: substation on rack makes me happy, here's how i define routes (using http_router): get :dashboard, '/dashboard'
<snusnu>
;)
<mbj>
snusnu: nice
<mbj>
snusnu: You need to start to use my request/request libs :D
<snusnu>
mbj: yeah, about that, i'm going to do that
<snusnu>
mbj: i also want to add one more feature to substation: "around chains" .. so basically, some api that allows you to define the first common request processors, and the last common response processors, and then you just stick "the unique part" in the middle
<snusnu>
mbj: initially i thought, cool, it will just work, i'll simply yield from within a chain definition, but it's not that easy, localjumperror .. but instance_exec will help, that plus the ability to nest chains already
cobbr2 has quit [Quit: Leaving.]
<mbj>
snusnu: Yeah good idea.
<mbj>
snusnu: I already searched for that feature :D
<mbj>
snusnu: We have to cleanup nameing on eurucamp
<mbj>
snusnu: And come up with more "primtive" nodes in a substation processing tree.
<snusnu>
mbj: i'm not sure what you mean by that, i agree with enhanced naming tho
<mbj>
snusnu: Substation concept is okay, but IMHO our primitive components are still to complex
<snusnu>
mbj: also, maybe, naming will converge towards a state machine
<snusnu>
mbj: i'm starting to think of it more as a state machine which happens to be "viewable" as a chain of responsibility
<mbj>
snusnu: yeah
<snusnu>
mbj: but i'm not sure … i think i will implement 1 or 2 last features for now, and then let it sink .. come back after a while, look at it with fresh eyes
<mbj>
snusnu: lets say it this way, I really like substation
<mbj>
snusnu: but somehow I feel it needs to be improved a lot.
<mbj>
snusnu: Just like all tools I like :D
<snusnu>
mbj: hah true, and yeah, feel free to send any ideas my way
<snusnu>
mbj: the other feature i mentioned, was keeping track of the different states in some object .. i want to be able to view a page that shows me the state at every processor, for debugging
<snusnu>
mbj: then i'm happy for now
<snusnu>
mbj: and also, won't have much time for it anyway
<snusnu>
:p
<mbj>
snusnu: Why not use the same design as ducktrap?
<mbj>
snusnu: having evaluator nodes with full istory?
<mbj>
snusnu: So you should be able to pretty print the "processing history" at a given point.
<mbj>
snusnu: Just like ducktrap can do.
<snusnu>
mbj: yeah, that's the plan
<snusnu>
mbj: feel free to PR
<snusnu>
heh
<mbj>
snusnu: I'm not familiar enough with substations internals. So my pr would be a rm lib + lots of new code :D
<mbj>
snusnu: So I'll not PR this :D
<mbj>
snusnu: Start with reading the internals first.
<snusnu>
mbj: lol ok
<mbj>
snusnu: Ans somehow it is easier to write new code thant extending existing code.
<snusnu>
yeah
<snusnu>
tho that's probably really not necessary at this point ;)
<mbj>
yeah
<snusnu>
anyways, re workshop, i'd be in
<mbj>
The parts of substation I already "got" are nice.
<mbj>
snusnu: nice!
<snusnu>
but i guess it'd need to be kinda adhoc?
<snusnu>
given at least i won't have any real time to prepare anything i guess
<snusnu>
not even the 5min substation lightning talk i wanna (and will) do
<snusnu>
:p
<mbj>
snusnu: I'm okay with adhoc
<mbj>
I'm working near to full time on/with this stack