Skip to main content

Deployment Instructions

Overview

CSGHub is an open source, trustworthy LLM asset management platform that can assist users in governing the assets involved in the lifecycle of LLM and LLM applications (datasets, model files, codes, etc). With CSGHub, users can perform operations on LLM assets, including uploading, downloading, storing, verifying, and distributing, through Web interface, Git command line, or natural language Chatbot. Meanwhile, the platform provides microservice submodules and standardized OpenAPIs, which could be easily integrated with users' own systems.

CSGHub is committed to bringing users an asset management platform that is natively designed for LLMs and can be deployed On-Premise for fully offline operation. CSGHub offers functionalities similar to a privatized Huggingface(on-premise Huggingface), managing LLM assets in a manner akin to how OpenStack Glance manages virtual machine images, Harbor manages container images, and Sonatype Nexus manages artifacts.

Instructions

This Helm Chart is currently in the testing release phase. If you encounter any issues, please submit feedback through the following channels:

This Helm Chart uses the helm package manager to bootstrap the CSGHub runtime environment on a Kubernetes cluster. By default, this Helm Chart is intended only for testing and trial purposes in non-production environments. For production deployments, please seek support through the above channels.

For production deployment, you should have extensive experience using Kubernetes, as this method differs significantly from deploying with docker-compose. While this approach offers convenient deployment, it also introduces maintenance complexities.

This architecture includes multiple stateful components, so Dynamic Provisioning of PV is essential for the program's operation. If you are using a self-deployed Kubernetes cluster, utilizing sig-storage-local-static-provisioner for dynamic PV management is a good option; otherwise, you may need to create PV and bind PVC manually.

The stateful components are as follows:

  • PostgreSQL
  • Minio
  • Registry
  • Redis
  • Gitea
  • Builder
  • Nats

Currently, each component only includes declarations for the necessary resource files required for startup. Extended features will be gradually added in the future, and we also look forward to your contributions.

Version Mapping

Chart versionCsghub versionRemark
0.8.x0.8.x
0.7.x0.7.x
0.5.x0.5.x
  • Note: There may be cross-mappings in the current version, so it is advisable to use the latest version for deployment.