On 6 September 2011 17:30, Warren Seen <[email protected]> wrote:
> 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. > That's the thing - the clients usually don't know anything about assets or similar. It should probably be hidden from them. But in any case we can probably start thinking in that direction. Thanks for the pointers. -- 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.
