Skip to content

Add support for indexing custom/private packages in a cloogle instance.

Gijs Alberts requested to merge GijsAlberts/cloogle-web:add-extra-packages-config into main

What does this MR do?

This MR adds support for indexing custom/private packages in a Cloogle instance.

This can be done by using a configuration file, named extra_package_config.json by default.

This contains a list of custom packages to index in the Cloogle instance.

As an example:

[
 {"name": "a"
 , "url": "gitlab-repo-url"
 , "maintainer": "TOP Software"
 , "deploy_token": "<deploy-token-read-package-registry-access>"
 , "license": "NONE"
 , "description": "d"
 , "latest_version": "1.0.0"
 , "versions":
  { "1.0.0":
   { "created": 1656418256
   , "targets":
    { "linux-x64": {"url": "https://gitlab.com/api/v4/projects/<project_id>/packages/generic/<package_name>/<version>/<package>-linux-x64.tar.gz"}}
   }
  }
 }
]

As cloogle-web is an application I think it is not necessary to add a CHANGELOG.md entry.

I could document this feature in the README.md if you wish.

Changes to public APIs

Author's checklist (required)

  • Intermediate commits compile (use git rebase -i main if not)
  • Newly added code has a style consistent with the rest of the repository
  • Newly added code is documented (guidelines)
  • If bugs have been solved, tests have been added (guidelines)
  • A changelog entry has been added (guidelines)

Related issues

Edited by Gijs Alberts

Merge request reports