On Tue, Apr 21, 2009 at 1:59 PM, thron7 <[email protected]> wrote: > Ralf, > > this thread stems from last year's August. Things have changed a bit...
The confusion comes from: http://qooxdoo.org/documentation/0.8/setting_a_different_application_root Which seems to be out-of-date for 0.8.2 The article you linked to seem to provide everything I could wish for. However, for now, I'll stick to the symlinking trick. Since I can keep all the server-side and client-side code together that way. I would look into it again, if I choose to setup seperate vhosts. (although it may be wiser to use custom routing & aliases, so it can share the same ruby instance) > Again, it's a matter of the development model. Not many people are > exposing their source version through a web server. But it should work > now nevertheless. Which makes sense for a pure javascript client-side application. But developing server-side code, with database migrations and specific server-side needs (like htmldoc packages and such), it's easier to just setup one central dev server and mount it with ssh. Greetings, Ralf ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
