Rails - Apr 2005 - Deploying with static content: best practices?

What''s the best way to be deploying relatively static content
alongside the rest of your webapp''s M,V & C? It seems like the best
way is to put such content in standalone rhtml files in your /views/
directory, referring to them with action-like URLs. So,
/interweb/contact_info.rhtml becomes /interweb/contact_info with no
extensions.

However, is there some better or cleaner way for putting this content out?

 d

Personally, I just put an attr_reader :contact_info in my controller and 
it''ll pass it on to the view. You could probably do a method_missing
that
does nothing, but for some reason I feel like thats too magical and could 
come back and bite you.

Should probably make an alias for attr_reader called "static_action"
or
something, for clarity.

-Jeff

----- Original Message ----- 
From: "Dev Purkayastha"
<dev.purkayastha-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: <rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org>
Sent: Tuesday, April 05, 2005 9:06 AM
Subject: [Rails] Deploying with static content: best practices?

> What''s the best way to be deploying relatively static content
> alongside the rest of your webapp''s M,V & C? It seems like the
best
> way is to put such content in standalone rhtml files in your /views/
> directory, referring to them with action-like URLs. So,
> /interweb/contact_info.rhtml becomes /interweb/contact_info with no
> extensions.
>
> However, is there some better or cleaner way for putting this content out?
>
> d
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

On Tuesday 05 April 2005 11:57, Jeffrey Moss wrote:
> Should probably make an alias for attr_reader called
"static_action" or
> something, for clarity.
If you did, you could make static_action tell Rails to cache the static 
page...

-- 

Nicholas Seckar aka. Ulysses