Rails 3.0 or 3.1 for first Jugg2 exploration?

[Bill Walton]

Hi,

I'm on vacation this week and want to have some fun. My job
responsibilities have kept me heads-down in Rails 2.3.x and I'm going
to do some "exploring." Thought I'd jump right to 3.1 but also want
to get my feet wet with Juggernaut. Ideally, I could explore both 3.1
and Jugg2 in the same (small) app. I'm wondering if that's a good
idea, where "good" has a "fits within the time constraints" component.
Vacations don't go on forever ;-). Any / all recommendations very
much appreciated!

TIA,
Bill

[Matt Chan]

Hi Bill,

I haven't tried Juggernaut with Rails 2.3.x, but I tried added it to a project at work that where I'm using Rails 3.0.x. Rails 3.1 is something I don't plan on moving to immediately, but I haven't had any problems integrating Juggernaut 2 and Rails 3 so far (also in a similar situation as you). The code that I'm using in Rails to publish an update to Juggernaut is small and minimal (straight from the GitHub wiki) that it doesn't interfere with the other Rails things I've coded. In your case, it might depend on what you want to use Juggernaut for and how. Maybe if you provided some more details, that might lead to some better advice.

Matt

[bill walton]

Hi Matt,

On Jul 25, 7:25 am, Matt Chan <chan.matt...@gmail.com> wrote:
> Hi Bill,
>
> I haven't tried Juggernaut with Rails 2.3.x, but I tried added it to a
> project at work that where I'm using Rails 3.0.x. Rails 3.1 is something I
> don't plan on moving to immediately, but I haven't had any problems
> integrating Juggernaut 2 and Rails 3 so far (also in a similar situation as
> you).

I'm not sure whether this is a 'problem' or not but not being able to
figure out which index.html is being rendered (new email / request for
help from me today) really has me perplexed. Another thing I realized
today is that I can't find a log that shows the render that's
happening. Wierd (for me). Any help much appreciated. I know I must
be missing / misunderstanding something simple.

I've also decided to just work with Rails 3.0 until I get juggernaut,
et. al, running and understood. No sense introducing any new unknowns
at this point ;-)

> The code that I'm using in Rails to publish an update to Juggernaut is
> small and minimal (straight from the GitHub wiki) that it doesn't interfere
> with the other Rails things I've coded. In your case, it might depend on
> what you want to use Juggernaut for and how. Maybe if you provided some more
> details, that might lead to some better advice.

I'm not sure exactly what I'm going to jump off on once I get past the
basics. My 'day job' is development lead for shopkeep.com which is a
point of sale system where the back end lives on aws and, among other
things, gives store owners visibility into what's going on in their
brick and mortar store when they're not there. There's been some
interest expressed in a stock ticker-like feature where they could see
what's 'hot' today. Might be a good place to start.

Thanks for the reply!
Bill
>
> Matt

[Matt Chan]

I still don't understand Rails very well (just enough)l, but for anything static in the public folder, I've never seen anything in the log about serving a static file. This is out of the box; I'm not aware of any Rails configuration that would do it.

What "index.html" files are you talking about? Your own index.html and the one provided by Juggernaut? I guess I don't understand what it is you are trying to do when you say that you don't know "which index.html file is being rendered."

This doesn't seem like a "problem" as you say, but what you're describing doesn't sound like it's an issue with Juggernaut + Rails integration. It sounds more of an architectural misunderstanding on your part. To answer the original question though, there probably isn't any difference in using Juggernaut with Rails 3.0 or Rails 3.1

Matt

[Bill Walton]

Hi Matt,

On Tue, Jul 26, 2011 at 10:28 AM, Matt Chan <chan.m...@gmail.com> wrote:
> What "index.html" files are you talking about? Your own index.html and the
> one provided by Juggernaut? I guess I don't understand what it is you are
> trying to do when you say that you don't know "which index.html file is
> being rendered."

When you start juggernaut and set your browser url to localhost:8080
it renders (by default) index.html. There were more than one
installed as I was getting all the pieces installed and I couldn't
figure out which one was getting rendered. Yesterday evening I got
back to looking at it and when I started juggernaut and browsed to
localhost:8080 it rendered the one located at
'/usr/lib/node_modules/juggernaut/public/index.html" I can tell
because it displayed the <h2> element that I added with that url as
the innerHTML. No idea yet why it wouldn't the first time(s) around.
Much more to learn. Hoping to get back to it tomorrow and get on with
the Rails integration.

Thanks,
Bill