HI all, Is there a way to add a new tenant to an existing deployment without wiping the db? the 'ant create_db import' step is necessary to instantiate the tenant info in the db but this also clears all other tables. This is for v3.0. Thanks, - Jesse

I've never tried this, but you might be able to accomplish this by running just the 'ant import' target. You'll probably see some complaint messages from Postgres about attempts to create duplicate rows, but those should be harmless. Again, I haven't tried this so no guarantees it will work. However, it seems like something we should gracefully support so please create a JIRA issue for this. Thanks, Richard On Nov 27, 2012, at 2:46 PM, Jesse Martinez <jmartinez@movingimage.us> wrote: > HI all, > > Is there a way to add a new tenant to an existing deployment without wiping the db? the 'ant create_db import' step is necessary to instantiate the tenant info in the db but this also clears all other tables. This is for v3.0. > > Thanks, > > - Jesse > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org On Nov 27, 2012, at 2:46 PM, Jesse Martinez <jmartinez@movingimage.us> wrote: > HI all, > > Is there a way to add a new tenant to an existing deployment without wiping the db? the 'ant create_db import' step is necessary to instantiate the tenant info in the db but this also clears all other tables. This is for v3.0. > > Thanks, > > - Jesse > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

We have talked a bit about "Clone a tenant" as one of the key tools we need to build for a SaaS offering, and this seems to fit in with that (although perhaps with a variant). The tools lack this kind of easy-to-use functionality at this point, but perhaps Richard's approach will suffice (with luck). Patrick On Nov 27, 2012, at 7:47 PM, Richard Millet wrote: > I've never tried this, but you might be able to accomplish this by running just the 'ant import' target. You'll probably see some complaint messages from Postgres about attempts to create duplicate rows, but those should be harmless. > > Again, I haven't tried this so no guarantees it will work. However, it seems like something we should gracefully support so please create a JIRA issue for this. > > Thanks, > > Richard > > On Nov 27, 2012, at 2:46 PM, Jesse Martinez <jmartinez@movingimage.us> wrote: > >> HI all, >> >> Is there a way to add a new tenant to an existing deployment without wiping the db? the 'ant create_db import' step is necessary to instantiate the tenant info in the db but this also clears all other tables. This is for v3.0. >> >> Thanks, >> >> - Jesse >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > On Nov 27, 2012, at 2:46 PM, Jesse Martinez <jmartinez@movingimage.us> wrote: > >> HI all, >> >> Is there a way to add a new tenant to an existing deployment without wiping the db? the 'ant create_db import' step is necessary to instantiate the tenant info in the db but this also clears all other tables. This is for v3.0. >> >> Thanks, >> >> - Jesse >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org