How to handle multiple systems using Doorstop?

[urbasus]

I would like to know how to integrate Doorstop over multiple systems. Any "success stories" appreciated.

In particular I have hard time realizing how multiple systems (or stakeholders) depending on a single system might work. Example being two subsystems using the same library service. Since Doorstop allows only one uplink/parent per item, there is no obvious way to make that work. As compared to a graph database putting no restrictions on link direction or count. This assuming it's all in the same repository.

Way-of-working with items external to the repository are also of interest, be that by submodule or package, uplink or downlink.

[JustinW80]

If you have multiple systems across multiple repositories, I agree that is probably messy. I haven't any experience yet trying to resolve that. Perhaps the doorstop --project PATH can specify the root of the tree you want to validate, but I haven't tried it.

Since Doorstop allows only one uplink/parent per item, there is no obvious way to make that work.

Right, Doorstop does not support child docs with multiple parents; see #292 .

[ckolumbus]

@urbasus could you maybe describe the scenario how you would envision such an integration? where would you decide for which projects the common requirements apply ? e.g. more a push model (the "parent" declares, which projects need to pick it up) or the pull model (the "child" documents say, which upper level docs are relevant) ??