Skip to content

Use chorus as a backend #4

@Lordakius

Description

@Lordakius

Ajour uses a subproject to create the addon catalog. For CH there is chorus which should serve the same purpose.

I am not sure if using subcrates (as done by ajour) is the best way, since the stuff is already pretty specialized and there is imho no real value in modularizing it. It might be good to design it so that the backend can be changed, but I doubt that I will support other backends in the near future.

I propose a file handling the API calls to chorus and providing the files to CHmon.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions