[daisy] One Daisy wiki, many repositories?

Olivier Lange wire at petit-atelier.ch
Tue Apr 1 21:15:13 CEST 2008


Hi John,

Thanks for the hint. I've also thought of that... running all sites within a single Daisy Wiki and single Daisy Repository. But I am not sure how I would *merge* my existing repositories. Is that even possible?

I just reread about the namespaces and import/export. AFAIU, I could go this path:

 * Of course, I would need to upgrade them to Daisy 2, as two of them are still Daisy 1.5.1.

 * Then I would have 5 different namespaces, each repository being responsible of maintaining the document ID's whithin its namespace.

 * With the export/import tools, I could migrate all schema, part types, fields types and documents from the 5 different repositories to a single repository. Versions would get lost.

 * I would recreate users, roles and rewrite the ACL -- which would get complex.

 * Yet, as I understood, this single main repository won't maintain the document ID's in the other namespaces.

But then, I am confused. What happens if a user adds a new document from within a site which was part of a migrated repository, whose documents are not part of the main repository? In which collection will the new document end up? I fear it won't be accessible anymore within the site it was created from.

A glimpse of the contents of some of my repositories:

repository RRSC:
  2 collections
  2 sites:
    site RP, collection RP
    site RA, collection RA
  1 language
  14 different document types, 15 part types, 50 field types
  20 users, "not so simple" ACL
  > 1400 documents, quite some version history

repository CFDE:
  2 sites:
    site CP, default collection CP
    site CA, default collection CA
  2 collections
  1 language
  4 different document types, 30 field types
  5 users, simple ACL
  > 800 documents

repository BUCB:
  1 collection
  5 sites:
    site FR, default collection BUCB
    site DE, default collection BUCB
    site IT, default collection BUCB
    site RM, default collection BUCB
    site BUCB, default collection BUCB
  4 languages
  2 different document types, 20 field types
  4 users, simple ACL
  > 600 documents

Olivier

--
Le Petit Atelier de Génie logiciel
t. +41-21-6487665, m. +41-76-5166212, http://www.petit-atelier.ch/


Kealy, John wrote:
> Oliver,
> 
> We are running 29 sites in one instance of the Daisy wiki and repository. We use apache as the front end and proxy jetty through various virtual hosts. 
> 
> I'd strongly recommend this approach as our me memory usage with that set up tends to be pretty small and we are running some sites that get a significant amount of traffic (~7,000 daily visits).
> 
> Best regards.
> 
> John Kealy
> 
> -----Original Message-----
> From: daisy-bounces at lists.cocoondev.org [mailto:daisy-bounces at lists.cocoondev.org] On Behalf Of Olivier Lange
> Sent: Wednesday, March 19, 2008 9:00 AM
> To: daisy-users
> Subject: [daisy] One Daisy wiki, many repositories?
> 
> Hi all,
> 
> Running side-by-side, I have 5 instances of Daisy (repo+wiki) on a Debian Linux server with 2GB of RAM.
> 
> When the wikis are under load, I noticed that the server started to swap memory and performance lowers for a while.
> 
> As adding RAM is not possible (hardware limit) and changing the hardware neither, I wonder if merging the Daisy Wikis into one single instance wouldn't lower memory consumption significantly?
> 
> I mean, provided Daisy powerful multi-site and skinning features, couldn't a single instance serve all sites, from different repositories?
> 
> The association between each site and it's repository should oviously be described (siteconf.xml?)
> 
> Does this make sense?
> 
> On the other hand, running distinct repositories instances is ok, as they consume less memory than the wiki, and they enforce separate document types, fields, users, roles and ACLs for each customer.
> 
> Just a wild guess: is it a matter of introducing new components within daisy.xconf for the distinct repositories, describing the binding between site and repository within siteconf.xml and having o.o.d.f.FrontEndContext figuring out what repository role to use, depending on the request?
> 
> Kind regards,
> Olivier
> 
> --
> Le Petit Atelier de Génie logiciel
> t. +41-21-6487665, m. +41-76-5166212, http://www.petit-atelier.ch/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3909 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.cocoondev.org/pipermail/daisy/attachments/20080401/9c151de9/smime.bin


More information about the daisy mailing list