The simplest way IMO to set up a directory for each subdomain/account (under public/) to which the client can upload any css/image assets their template requires - or buckets on S3 if you're using heroku. If you start this way then it clears the way for you to allow clients to manage their own template assets later on down the track.
As I said, we're really just beginning, and I'm sure there's more sophisticated ways we can manage this, but right now it's a case of doing the simplest thing that works - it helps that the templates are all for different identities for the same client, so they're not overly concerned with being able to share stylesheets/assets between templates, etc. On 06/09/2011, at 5:08 PM, Dmytrii Nagirniak wrote: > On 6 September 2011 16:17, Warren Seen <[email protected]> wrote: > It may or may not be the right approach for you, but we're beginning to use > liquid templates for custom views per-subdomain in a multi-tenanted app. > Maintaining a separate set of views for each subdomain doesn't scale well. > > Check it out here: http://www.liquidmarkup.org/ > > That's another option. Never tried liquid before. How do you deal with assets? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
