RoR Homepage Question

[devanium]

What's the standard practice for creating application homepages if it's not designed as a part of an existing controller? For example, I want to include data from multiple controllers on my homepage. Do you just create an index controller specifically for that purpose?

Thanks!

[IAIHMB]

That's fine, I call mine a dashboard. By the way, the link in your signature appears to be hacked.

[devanium]

That's fine, I call mine a dashboard. By the way, the link in your signature appears to be hacked.

Do you use that for all your static pages then? Like "About Us", "Learn More", etc?

Thanks for letting me know about the hacked forum too... don't these people have better things to do?

[IAIHMB]

Nah, I used dashboard on a project that I'm currently working on, but it varies on a project by project basis. You really can't go wrong, you could have a static controller with about and information actions.

[devanium]

Nah, I used dashboard on a project that I'm currently working on, but it varies on a project by project basis. You really can't go wrong, you could have a static controller with about and information actions.

Alright, cool, thanks! Also, thanks for letting me know about Mongrel on that other thread - works like a charm, and a lot easier/faster for development. I think I'm going to use it with LiteSpeed when I deploy...

[IAIHMB]

I should probably clear a few things up, I was a bit pressed for time. If I had a controller named static with about and information actions I would probably route /about to the static controller's about action and /information to the static controller's information action (As apposed to /static/about and /static/information.). You could generate a controller for each, but that's not good practice.

LiteSpeed is really nice, don't forget to set contexts for your static content.

[devanium]

I should probably clear a few things up, I was a bit pressed for time. If I had a controller named static with about and information actions I would probably route /about to the static controller's about action and /information to the static controller's information action (As apposed to /static/about and /static/information.). You could generate a controller for each, but that's not good practice.

LiteSpeed is really nice, don't forget to set contexts for your static content.

Yeah, I'm having the index controller do all of that, then modified routes.rb to point to it... works great! Thanks for the tips.