You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose the implementation of custom App "Registries" in Puter, a feature that allows users and developers to establish separate destinations:
within the App Center for loading a list of apps together with their metadata
and within the Dev Center for publishing apps
Details
The feature will introduce a new level of organization and customization to the Puter ecosystem, enhancing the flexibility and control users and developers have over app distribution and availability.
Users and developers will have the ability to manage custom registries (additional to the default puter.com) through a settings section/window, which will be part of and shared between both the App Center and Dev Center.
For the backend side, this feature requires the development of a dedicated service or the extraction and adaption of relevant parts from the main Puter code to handle registry management tasks, including the storage and retrieval of registry data.
Technical Considerations
To implement this feature, it would be necessary to:
create a shared management GUI for custom App "Registries", accessible from both the App Center and Dev Center, to create, edit, and delete them.
implement the required backend service or extract the current implementation parts from the main Puter code.
improve the way how apps are loaded via the /app/* URL to allow users to specify the registry to use for finding the app (e.g. <app name>@<registry domain>)
Potential Future Enhancements
Integration of registry-specific analytics to track app usage and popularity within each registry.
Enhanced security features for registry management, including role-based access controls.
Development of an API for automated registry interactions by third-party tools and services.
The text was updated successfully, but these errors were encountered:
This is a great idea. In fact, we started work on this internally but had to pause because of some other high priority tasks that came up. I think this is a natural progression of how Puter is and we'll definitely make it happen.
Edit: we'll resume work on this soon. But PRs are definitely welcome.
I propose the implementation of custom App "Registries" in Puter, a feature that allows users and developers to establish separate destinations:
Details
The feature will introduce a new level of organization and customization to the Puter ecosystem, enhancing the flexibility and control users and developers have over app distribution and availability.
Users and developers will have the ability to manage custom registries (additional to the default puter.com) through a settings section/window, which will be part of and shared between both the App Center and Dev Center.
For the backend side, this feature requires the development of a dedicated service or the extraction and adaption of relevant parts from the main Puter code to handle registry management tasks, including the storage and retrieval of registry data.
Technical Considerations
To implement this feature, it would be necessary to:
/app/*
URL to allow users to specify the registry to use for finding the app (e.g.<app name>@<registry domain>
)Potential Future Enhancements
The text was updated successfully, but these errors were encountered: