On Fri, Aug 20, 2010 at 00:37, Benoit Chesneau <[email protected]> wrote:
> On Thu, Aug 19, 2010 at 7:22 PM, Jason Smith <[email protected]> wrote: > > On Fri, Aug 20, 2010 at 00:13, Benoit Chesneau <[email protected]> > wrote: > > > >> A couchapp should be "domain" independant, this is the principle of a > >> couchapp . So I can replicate anywhere and not only in > >> centralizedhost.com . Following this principle, it sound weird to set > >> an hostname in the CouchApp. > >> > > > > That is true. > > > > But partially, the reason couchapps run immediately after replication is > > because all couchapps are still very simple. In the future they will be > like > > The mature PHP apps. First you copy to the target. Then you run a > one-time > > config to input your email address, site name, theme preferences, etc. > etc. > > In there might be the vhost/rewrite questions. > > > there is no reason to not keep the simplicity while the couchapps > feature grow. And I personnaly hope that CouchDB will help to remove > the need of a centralized hosting and just use these services as a > facility to put online for a time our data. > > But that's just the way I see it. Today it's already possible to had > an hostname to any couchapp and write an handler listening on each dbs > to get updates in ddocs and then set hostname. > > What could be interresting is y to ease management of modules in > couch so you can add your mod_vhost like you can do on apache. > I am also very interested in that. It is very easy with Erlang modules. I think the only problem is not many people know Erlang. When I wrote my first auth handler, it was I think 15 lines of code. And I edited local.ini. Voila! -- Jason Smith Couchio Hosting
