tabularium
Self-hosted plugin registry for the tabularis platform with multi-provider submission (GitHub, GitLab, Gitea), signed releases, a built-in CMS, and support for multiple database dialects.
Ficha actualizada 22 sept 2026, 18:47 · upstream 22 sept 2026, 18:04 · release v0.14.2
Qué es tabularium
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
Tabularium is a self-hosted plugin registry designed to index, submit, and discover plugins for the tabularis platform. It provides a web UI with OAuth-driven submission flows, an OpenAPI surface, and a built-in content management system. Authors connect their GitHub/GitLab/Gitea accounts, select a repository, and receive automated release webhooks upon tag creation. The registry supports multi-language READMEs, plugin kind taxonomy, install wizards, and desktop handoff via URL schemes.
Under the hood, Tabularium is built on Bun as its runtime engine, Elysia for HTTP services with TypeBox validation, Drizzle ORM for database abstraction across SQLite, PostgreSQL, and MySQL, and Eden Treaty for end-to-end type safety. It features a Docker image available at codeberg.org/Tabularium/Tabularium, along with k3s manifests for Kubernetes deployment.
The platform supports multi-dialect databases (SQLite, Postgres, MySQL), feature toggles to disable submissions without redeploying, audit logging of all admin mutations, and a modular project layout that separates the API, frontend, client SDKs, manifest validator, CLI tool, and Rust async client.
- Onboarding new plugin authors by providing an automated GitHub/GitLab/Gitea integration with release webhook generation
- Centralized discovery of plugins across multiple repositories through a unified web interface
- Managing plugin metadata including descriptions, documentation, and kind taxonomy for better organization
- Enforcing security standards via signed releases (SHA-256 hashed + Ed25519 signature) with GitHub build-provenance relay
- Reducing manual maintenance of release manifests by automating webhook generation on every tag push
- Extending the platform with custom plugin kinds through an admin-defined taxonomy system
- Built entirely in Bun, offering a fast and developer-friendly runtime environment
- Supports multiple database dialects (SQLite, PostgreSQL, MySQL) via Drizzle ORM
- Signed releases with Ed25519 key signing and JWKS at /.well-known/registry-key.json
- Multi-language README support with locale-specific serving from the manifest
- Built-in CMS with markdown pages, widgets, and per-locale translations
- OpenAPI surface for programmatic plugin submission via Elysia + TypeBox
- The Docker image is currently published on Codeberg rather than a public registry like GitHub Container Registry or NPM
- Feature toggles require a redeploy to take effect, which can introduce downtime during feature rollouts
- No built-in CI/CD pipeline for automated testing of plugin submissions before release
- The install wizard uses SQLite by default and requires manual configuration for PostgreSQL or MySQL connections
- Documentation is hosted on tabularium.wiki rather than a centralized documentation site
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Use the published Docker image from codeberg.org/Tabularium/Tabularium, replacing docker-compose.example.yml with docker-compose.yml,Generate secrets using openssl rand -hex 32 for JWT_SECRET and TOKEN_ENC_KEY before editing compose files,For PostgreSQL: set DATABASE_URL to 'postgres://user:pass@host:5432/db',For MySQL: set DATABASE_URL to 'mysql://user:pass@host:3306/db',Run `docker compose up -d` to start the registry, then navigate to http://localhost:3000 for the install wizard,To develop locally, run `just dev` which starts minikube with Tilt up a postgres + dragonfly environment,The bootstrap password is printed on first boot and must be entered during the install wizard,For Kubernetes deployment, use the k3s manifests in the deploy/ directory as provided by the Forgejo Actions workflow
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.