Unfortunately not, Rodrigo. Frankly, TorqueBox on OpenShift is not a very happy experience, mostly due to bundler and very limited resources on the free OpenShift gears. Until we get those issues worked out, I don't want to encourage anyone to combine TB and Immutant on OpenShift.
Also, we're kinda in a wait-and-see mode while the OpenShift guys integrate Docker, as container images should be a lot easier to work with than cartridges. So you're ahead of us at the moment. We expect to catch up, just not sure when. Jim On Thu, Oct 24, 2013 at 8:45 PM, rdelcueto <rdelcu...@gmail.com> wrote: > Dear Jim, > > I just began playing with Immutant and TorqueBox. > I realized the polyglot-openshift-quickstart* @ *GitHub is marked as > obsolete. I found links to newer versions of immutant-quickstart and > torquebox-quickstart, though as separate applications. > Is there documentation or a tutorial on how to get TorqueBox and Immutant > merged into a single OpenShift application, ala "lein immutant overlay > torquebox"? > > Regards, > > > On Monday, September 9, 2013 11:14:54 AM UTC-5, Jim Crossley wrote: > >> Hi Rodrigo, >> >> I'm one of the developers of TorqueBox and Immutant. Your email prompted >> me to re-watch a screencast [1] I made in March showing how to use them >> together. I realized things have changed a little since then, so I added a >> few annotations to the video highlighting the differences. Hopefully enough >> to get you up and experimenting. >> >> As you've probably figured out, both TorqueBox and Immutant are >> integrated stacks, bundling some commodity services that most non-trivial >> applications need, e.g. scheduling, caching, and messaging. The intent of >> any integrated platform is to relieve administration burden. But that only >> works for you if the inherent choices within that stack fit the needs of >> your app. We think/hope default Immutant configuration and abstractions >> (e.g. queues, topics, request/respond) offers a good balance to fit a wide >> variety of apps. >> >> If simple integration between Ruby and Clojure apps is your chief goal, I >> think Immutant/TorqueBox is compelling, but I'm biased. I would definitely >> recommend using some sort of messaging broker, though, i.e. don't mix >> Clojure and Ruby in the same source file or project. >> >> Performance and security concerns are so application-specific I hate to >> make any generic statements about them other than, "be fast and secure". ;-) >> >> But do feel free to bother us in #torquebox or #immutant on freenode with >> any questions about your particular app/needs. >> >> Thanks, >> Jim >> >> [1] >> http://immutant.org/news/**2013/03/07/overlay-screencast/<http://immutant.org/news/2013/03/07/overlay-screencast/> >> >> >> >> On Sun, Sep 8, 2013 at 10:25 PM, rdelcueto <rdel...@gmail.com> wrote: >> >>> Hi everyone, >>> I'm about to start working on building a site for a startup company. >>> >>> We are a small team, and currently they've been coding the site using >>> RoR (Ruby on Rails). I was thinking Clojure might be better suited for the >>> task, specially because we'll need to implement a backend which is robust, >>> scalable and secure, but also we'll need flexibility, which I think the RoR >>> framework won't shine at all. >>> >>> At our team, we are two coders, non of us are proficient in Web >>> Developing, and we have little experience with RoR, and I thought (I'm >>> sure) maybe investing time learning Clojure will provide us with better >>> tools. >>> >>> PROBLEM/QUESTION >>> >>> While searching for alternative solutions, I stumbled upon the >>> Flightcaster case, we're they are using RoR to implement the site's >>> frontend and Clojure for the system backend. I thought this was a very >>> elegant solution, using each tool for what it's good at. Plus this way we >>> can reuse what they've already implemented. >>> >>> I found a way to do this is by using Torquebox and Immutant, and using >>> the messaging systems to communicate between Jruby and Clojure. Still I >>> have no idea of how this works, and the performance and security >>> implications it brings to the table. I found little information on the >>> subject. >>> >>> I would appreciate if anyone could provide guidance, examples or >>> documentation on the subject. >>> >>> Any reference to open source projects which use this hybrid language >>> solutions on the JVM would be great to have. >>> >>> Is this the best way to solve the RoR interactions? Is there any other >>> way? >>> >>> Thanks in advance and best regards, >>> >>> Rodrigo >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@googlegroups.com >>> >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+u...@**googlegroups.com >>> >>> For more options, visit this group at >>> http://groups.google.com/**group/clojure?hl=en<http://groups.google.com/group/clojure?hl=en> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to clojure+u...@**googlegroups.com. >>> >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
