Cross Project Usage

[Lypsolon]

Currently, when an AyonCppApi instance is created, it needs the AYON_PROJECT_NAME environment variable to get overwrites from the server.
It would be great if we find a way to allow for multiple projects to be registered, maybe allow adding projects via func() call so that cross-project resolution is possible

[Lypsolon]

I'm just leaving this here.

I thought about the problem that if we load all the root_replace variables at startup, we would not know to what project they belong, but we can get the project name from the URI.

So maybe it's a good idea to build a nice function to disassemble a URI?

[Lypsolon]

Update:
when hitting the resolve endpoint we can get back the project name we could then build the get_seite_roots function in the api as a cache, aka it would have a unordert map that then stores the already stored site roots and when a new one is requested we then ask the server for it.

this assumes that we dont allow chaining the site roots at runtime, i argue this would be crazy to allow because paths dont get resolved a second time from the resolver so you would end up with a path mix and i see this causing errors.
im also missing a situation where changing the site roots at runtime would be needed.

currently thats not the case because we use the path only flag: we could ask martin to change the flag to also return the project, or give us a second flag, using no flag is not a good idea to much data send over the network, a byte less metters if we want to resolve 100k paths.

[dee-ynput]

Hello @Lypsolon
I'm lowering the priority and impact on this until we have a request for it.
Marking it as ready though 👍