Change Details

Currently, the way swh-graph is deployed on granet is as a single python process (async but still), the aiohttp server, which itself starts the java grpc server. This prevent from having several python HTTP servers running, and thus the java grpc server lifecycle should be made independent from the python loegacy code.

Currently, the way swh-graph is deployed on granet is as a single python process (async but still), the aiohttp server, which itself starts the java grpc server. This prevent from having several python HTTP servers running, and thus the java grpc server lifecycle should be made independent from the python legacy code.

Currently, the way swh-graph is deployed on granet is as a single python process (async but still), the aiohttp server, which itself starts the java grpc server. This prevent from having several python HTTP servers running, and thus the java grpc server lifecycle should be made independent from the python loegacy code.