Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Allow content-forests-per-host=0 #653

Closed
grtjn opened this issue Aug 25, 2016 · 2 comments
Closed

Allow content-forests-per-host=0 #653

grtjn opened this issue Aug 25, 2016 · 2 comments

Comments

@grtjn
Copy link
Contributor

grtjn commented Aug 25, 2016

Would allow hooking up to an existing database with:

content-forests-per-host=0
content-db=some-other-db

It only needs replacement of xs:positiveInteger by xs:integer in setup.xqy (3 times).

Need to check wipe, but I thought that was safe too..

@grtjn
Copy link
Contributor Author

grtjn commented Jun 8, 2017

In retrospect I don't think this makes sense. If someone wants to use an existing database as content-db, it is best to remove the section for the content-db from ml-config.xml entirely. It will prevent accidental creation, and changing of settings at bootstrap, and also prevent accidental removal at wipe.

@grtjn
Copy link
Contributor Author

grtjn commented Jun 8, 2017

@grtjn grtjn closed this as completed Jun 8, 2017
@grtjn grtjn self-assigned this Jun 8, 2017
@grtjn grtjn added this to the May 2017 milestone Jun 8, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant