CoArchi Model Import

[Gemini]

Hello,
When I add a local model to a workspace or publish it to a Git repository, it is published under the model root folder "model" in the master branch; however, I would like to publish it in a different folder of the Git repository with a different model root folder name.
How can I do that with the Archi Collaboration Plug-in?

   

[Phil Beauvoir]

You can't. It's coded that way.

[Gemini]

I believe it should be changed:)

[Phil Beauvoir]

I believe it should be changed:)

Well, it won't be changed.

[Gemini]

Why?

[Phil Beauvoir]

Why?

It's internally coded that way, and it won't change. However, the good news is that coArchi is free and open source so you can fork the code and change it in your own fork, if you wish.

[Jean-Baptiste Sarrodie]

Hi,

Why?

Because in the context of coArchi, git technology should be considered a black box managed only by the plugin. The same way you wouldn't expect to be able to change the internal database schema of a commercial software, and you're aware that attempting to do so would brake the software, storing other files into the git repository assigned to the model or using manual git commands on it would most certainly lead to a model corruption.

In short, the fact that coArchi uses a known and open storage system doesn't allow you to do silly things with it (for your own "safety").

Regards,

JB

[Gemini]

Thanks for your detailed replies.
I understand that each model is stored in its own Git repository with the model/ root structure. This works well for individual projects, but I'm looking for a way to organize multiple models efficiently while keeping each in its own repository.

Would it be possible to manage multiple model repositories under a parent repository—for example, by using Git submodules? That way, each model stays in its own Git repo, but everything is grouped together for easier access and management.

Would this approach work smoothly with coArchi, or are there any potential pitfalls I should be aware of? Are there other recommended ways to handle multiple repositories while keeping things structured and easy to work with?

[Jean-Baptiste Sarrodie]

Hi,

This works well for individual projects, but I'm looking for a way to organize multiple models efficiently while keeping each in its own repository.

This works well in all cases (I manage dozens of models for more than 10 teams all around the world).

Would it be possible to manage multiple model repositories under a parent repository—for example, by using Git submodules? That way, each model stays in its own Git repo, but everything is grouped together for easier access and management.

See my previous comment (especially the "silly things" part).

Would this approach work smoothly with coArchi, or are there any potential pitfalls I should be aware of?

Totally unsupported and most likely won't work.

Are there other recommended ways to handle multiple repositories while keeping things structured and easy to work with?

Yes : use one repository per model and a good git management system such as Git Lab. In Git Lab you can create your own hierarchy of groups and projects (ie. repositories), and manage access-right at any level. That's how I (and other people) do.

Regards,

JB