That's a nice solution :). If you ever need super speed with Hobo, you can try the caching tags: http://www.hobocentral.net/tutorials/caching. I've used them along with Turbolinks and the results are amazing :).
Regards, Ignacio El 29/06/13 02:00, Peter Booth escribió: > For what it's worth, I've gone the other way: wanted to use hobo for > site admin, but realized that the public face of my website really > didn't need to be dynamic. > > Solution was to use hobo/rails to build relational model and then > generate a static website using erb and some page build scripts. This > way the paying customers get a site that's stunningly fast and, more > importantly, can't have outages. I have cron jobs that regenerate the > site every few hours. The owner uses the hobo app to update data and > within a couple if hours she can see the results of her changes. > > Sent from my iPhone > > On Jun 28, 2013, at 4:46 PM, kevinpfromnm <[email protected] > <mailto:[email protected]>> wrote: > >> Since you seem to have at the heart of it, 2 types of activity I'd go >> with just 2 sites. One for the members, and one for the >> administrative functions while based on the user, they might only see >> a subset of the administration actions/views. If there's a 3rd type >> of activity, that doesn't really fall under the admin style, you might >> want a site for that. >> >> On Friday, June 28, 2013 8:00:55 AM UTC-6, hbaragar wrote: >> >> Hello all, >> >> What are the decision points used to determine if one should be >> using a subsite instead of just permissions? >> >> For example, an athletic might have the following kinds of users: >> >> * members >> * receptionists, who can perform a restricted set of activities >> on behalf of the members >> * club professionals, who >> o are member like in that they do the same things that >> members do >> o administer members (including doing some actions on behalf >> of members) >> o set up and administer athletic program (e.g. leagues) >> * club assistants, who have a subset of club pro functionality >> * club administrators, who manage receptionists, club >> professionals and assistants >> * system administrators, who manage club configuration and club >> administrators >> >> It doesn't make sense to set up a separate subsite for each kind >> of user because there is a lot of common functionality for some >> kinds of users. Should I separate subsite for major functional >> areas? Should I even use subsites? >> >> Has anyone developed a hobo application with more than one >> subsite? If so, are there any suggestions or lessons learned that >> you can pass on to me? >> >> Regards, >> Henry >> >> -- >> Henry Baragar >> Instantiated Software Inc. >> http://www.instantiated.ca >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Hobo Users" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected] >> <mailto:[email protected]>. >> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> Visit this group at http://groups.google.com/group/hobousers. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > You received this message because you are subscribed to the Google > Groups "Hobo Users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/hobousers. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Ignacio Huerta Arteche http://www.ihuerta.net Teléfono: 0034 645 70 77 35 Email realizado con software libre -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/groups/opt_out.
