All source repos should have some reasonable README.md which explains what the repo contains. I have not checked if its really the case but at least some information should be there.
@irreleph4nt said in Clarification on a few components needed:
The packages in question below. I’d appreciate it a lot if someone can please jump in and answer questions 1 - 3 for them individually, please.
grapi (kopano stash): this looks like a python module to me, but does it require the actual API server software called “grapi” as well to function?
This is the grapi service (forked out from kopancore) which is to be used by kapi via its grapi plugin. The separate grapi repository is still wip but future releases of grapi will be from this repository. In general grapi provides a service and is to be started by systemd. The service provides sockets which are consumed by kapi via its corresponding plugin to provide Kopano Groupware REST API endpoints.
kpop (git): has a Makefile and creates an “es” folder with yarn. That’s about all I have found out so far. :(
Kpop is a shared component library for our new web clients like Kopano Meet. It is used as build dependency via Yarn like other Javascript projects.
libkcoidc (git): looks to me like a library. Is this one needed for kopano-server (at buildtime) so that the server works correctly
with konnect? I know that this is build with go but where do the compiled files need to be so kopano-server and others can pick them up?
Libkcoid is a libary implementing Kopano relevent client parts for OpenID Connect. It provides interface for C, Go and Python. It is used by all Kopano services which interact or validate OpenID Connect tokens as a compile time depdency (simetimes optional, like for kopancore).
Generally for all our projects, there is a Makefile to build stuff from source. the projects README should contain information about build dependencies and further instructions if required.
