multi-repo project/framework configuration
Posted: Sat May 11, 2024 1:14 am
Hi Oxygen experts ...
I'm in the midst of a re-architecture idea, which would break up our DITA mono-repo into separate repositories: DITA-tooling, generated-content, authored-content. The generated and authored content is built by the tooling and these repos have versioning and configurations that are dependent upon each other. In a Windows-only environment, with only Oxygen Editor (with its Java 17), DITA-OT 4.2, and command-line git as dependencies, I'd like to create a UI where authors can select various configurations and obtain the appropriate branches of the three repositories. I can work out the dependencies, but I'm struggling to find the best method of providing a user experience that isn't more complicated than the old monorepo method of just checking out the branch with all the tools and everything together. Maybe a web page hosted by a java httpserver[1]? ..a UI presented by Oxygen with values stored in the project file or framework folder[2]? ... ?
Thanks for any guidance or ideas folks can provide.
Cheers!
- Gary
[1]: I mentioned the web page instead of swing, because my JavaScript experience is much stronger than Java.
[2]: This is the option I'm hoping for.. sharing a project/framework where config values can be easily selected as appropriate, saved as properties, and to kick off git checkouts, etc., through different ant targets.
I'm in the midst of a re-architecture idea, which would break up our DITA mono-repo into separate repositories: DITA-tooling, generated-content, authored-content. The generated and authored content is built by the tooling and these repos have versioning and configurations that are dependent upon each other. In a Windows-only environment, with only Oxygen Editor (with its Java 17), DITA-OT 4.2, and command-line git as dependencies, I'd like to create a UI where authors can select various configurations and obtain the appropriate branches of the three repositories. I can work out the dependencies, but I'm struggling to find the best method of providing a user experience that isn't more complicated than the old monorepo method of just checking out the branch with all the tools and everything together. Maybe a web page hosted by a java httpserver[1]? ..a UI presented by Oxygen with values stored in the project file or framework folder[2]? ... ?
Thanks for any guidance or ideas folks can provide.
Cheers!
- Gary
[1]: I mentioned the web page instead of swing, because my JavaScript experience is much stronger than Java.
[2]: This is the option I'm hoping for.. sharing a project/framework where config values can be easily selected as appropriate, saved as properties, and to kick off git checkouts, etc., through different ant targets.