I vote number 2 - it keeps apps separated, so you can pop a whole bunch in a folder and call it a day - Having one big shared public folder is messy and breaks that model of separation entirely. If people like Isak have existing arrangements in place, there aught to be some configurable option to specify any arbitrary folder as the public files.
— Jenna Fox On Tuesday, 20 December 2011 at 9:19 PM, Paul van Tilburg wrote: > On Tue, Dec 20, 2011 at 11:06:09AM +0100, Isak Andersson wrote: > > I think Alternative 2 makes the most sense. Then you can have multiple apps > > that don't share the public folder. Plus, you put almost everything in the > > app folder anyways so there shouldn't be a difference now either. > > > > > Alternative 2: > > > > > > app.rb > > > app/public > > > app/public/style.css # example > > > > > > > > > > I disagree. In most cases there is only one app (at least for most of > my apps). So I have an app.rb with stuff under public/. > > If there are more apps, there is no way of knowing whether they are > designed to work together and share the same public data, or they are > apps with seperate(d) public data. Since one has to build the URLs in > the app anyway, why not let the developer decide the layout of public/ > to suit a shared or seperated layout? (One can think of shared > stylesheets, but different sets of icons/PDFs/whathaveyou). > > Kind regards, > Paul > > -- > Web: http://paul.luon.net/home/ | Email: p...@luon.net (mailto:p...@luon.net) > Jabber/GTalk: p...@luon.net (mailto:p...@luon.net) | GnuPG key ID: 0x50064181 > _______________________________________________ > Camping-list mailing list > Camping-list@rubyforge.org (mailto:Camping-list@rubyforge.org) > http://rubyforge.org/mailman/listinfo/camping-list > >
_______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
