2011-04-01 07:44:20 utc |
jmettraux |
Joelio: hello and welcome to #ruote |
2011-04-01 08:57:43 utc |
Joelio |
jmettraux: Hi! |
2011-04-01 08:58:00 utc |
Joelio |
oops, always the way.. |
2011-04-01 08:58:18 utc |
tosch_le |
Joelio: Hi :-) |
2011-04-01 08:58:36 utc |
Joelio |
I'm considering using ruote within an automated provisioning system I'm planning for $WORK |
2011-04-01 08:58:53 utc |
Joelio |
tosch_le: Hello! glad I'm not talking to myself then :) |
2011-04-01 08:59:48 utc |
tosch_le |
:-) |
2011-04-01 09:00:09 utc |
Joelio |
.. bascially I'd like to take orders from the CRM and use ruote to make decisions on how to split the tasks down into it's constituent components and also get an admin sign-off to commence the task lists |
2011-04-01 09:00:20 utc |
Joelio |
anyone else using it for similar use cases? |
2011-04-01 09:02:35 utc |
tosch_le |
kenneth kalmer is using ruote for something in that direction, unfortunately his blog seems to be down |
2011-04-01 09:04:19 utc |
tosch_le |
you could have a look at http://jmettraux.wordpress.com/2010/08/30/rocking-the-enterprise-with-ruby/ |
2011-04-01 09:15:13 utc |
Joelio |
tosch_le: Yes, not read the full thing but I can see words like DNS / IP / Provisioning.. I work for an ISP so that's up my street.. cheers! |
2011-04-01 09:22:38 utc |
Joelio |
Wow, some of the ideas are exactly in-line with mine, which is good news! |
2011-04-01 09:25:14 utc |
Joelio |
I'm looking at using datamapper and and resque instead, but the philosophy is the same :) |