Details
-
Improvement
-
Resolution: Won't Do
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
3
Description
The config files mentioned in %subj% are often taken as "default"/"best practice" by users and used without deeper thought for configuration provided. This often results in decisions about storage that are sub-par at best. Aim of the ticket is to improve the situation by following:
- rename said files
- ditch "bundle" and "search" from name converting jackrabbit-bundle-mysql-search.xml to just jackrabbit-mysql.xml
- for remote DB setups (mysql, postgres, ingres) provide two separate configuration for the different setup:
- one using currently provided setup (PersistenceManager in DB, FileStore and DataStore in FS)
- one with everything in DB only
- name each setup as appropriate using extra suffix (that suffix will be used only for remote DB configurations so NOT for H2 or Derby)
- explain purpose of the config file in html comment on top of each file (one is providing (in most cases) better performance, but is more difficult to backup/restore due to split in storage, while other is easiest for backup/restore since all is in one place, but might be slower (depending on performance of DB and network in given setup))
at the end there should be 9 config files provided by us:
jackrabbit-derby.xml jackrabbit-h2.xml jackrabbit-mysql-filestore.xml jackrabbit-mysql-dbstore.xml jackrabbit-postgres-filestore.xml jackrabbit-postgres-dbstore.xml jackrabbit-ingres-filestore.xml jackrabbit-ingres-dbstore.xml jackrabbit-memory.xml
The naming above is just proposal, as part of the ticket, please suggest final naming for different configurations. Other variants considered have been (so far):
- jr-mysql-filesystem.xml vs jr-mysql-only.xml
- jr-mysql-and-fs.xml vs jr-mysql-only.xml
- jr-mysql-and-fs.xml vs jr-mysql-db-only.xml
- Also part of this ticket is to improve documentation
- add commented section to config files explaining which part of configuration is relevant to what
- update https://documentation.magnolia-cms.com/display/WIKI/How+to+install+PostgreSQL+as+the+persistence+provider+for+Magnolia and related siblings for other DBs (mysql, ingres, ...) with current content and move them to the official documentation. Perhaps even include link to official docu for given DB from comment in each config file
Checklists
Acceptance criteria
Attachments
Issue Links
- mentioned in
-
Page Loading...