Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions website/community/registries.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
title: Registries
---

These registries are available from other developers for managing Premake modules and libraries. If you have created a registry you would like to share, feel free to [add a link](https://github.com/premake/premake-core/edit/master/website/community/registries.md) to the list!

## Premake Manager

The following registries are fully integrated with **premake-manager**.

### [Common Registry](https://github.com/lolrobbe2/premake-common-registry)

A collection of public and popular libraries designed to integrate seamlessly with **premake**.

* **Dependency Management:** Libraries can declare dependencies, version ranges, and more.
* **Version Matching:** The `premake-manager-cli` automatically matches and installs the correct versions.
* **Customizable:** These registries are created via GitHub repositories and premake manager; users can create their own common registries and add them to their specific workflows via **premake-manager-cli** and derived extensions.

### [Public Registry](https://premake-registry-ywxg.onrender.com/)

The public registry is a hub for individual Premake users who want to share their libraries and modules with the community.

* **Easy Registration:** Modules can be registered via a web UI using GitHub login.
* **Flexible Integration:** While they integrate with `premake-manager-cli`, they are also designed to be used standalone (e.g., as Git submodules).
* **Search API:** Provides a public API dedicated to searching for available modules and libraries, allowing for integration into external tools and scripts.

---

> [!NOTE]
> Developers are encouraged to create their own common registries to manage internal dependencies within their team's specific Premake workflow.
Comment on lines +7 to +30
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is way too much information and reads like this is an official part of Premake - especially with the note at the end. This should follow the same format as Modules and Extensions, where each item is just a single line with just enough information to know what it is.

Something like this:

## Registries

- [premake-common-registry](https://github.com/lolrobbe2/premake-common-registry) : The common registry for [Premake Manager](https://github.com/lolrobbe2/premake-manager).

3 changes: 2 additions & 1 deletion website/sidebars-community.js
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ module.exports = {
'support',
'showcase',
'extensions',
'modules'
'modules',
'registries'
]
};
Loading