[ foo/build/dspace.war -> webapps/dspace-foo.war, baz/build/dspace.war -> webapps/dspace-baz.war ]
Sounds like what we do here on our development host. Each developer gets a database, a uniquely named [dspace] directory, and a precreated zero-length .war to let him drop his webapp on. It works pretty well, although developers are now asking for multiple instances each and I'm going to have to loosen up DBMS permissions a bit to let them do more themselves. I am curious, though, as to whether it's really okay to have several instances banging on the same database. In some cases it would be useful to have two different config.s, or even two different revisions of the same base version, working on the same assets for easy comparison. Has the code been written with concurrent updates from multiple instances in mind? -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpxOus5wgK4R.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
