mirror of
https://github.com/apache/superset.git
synced 2026-05-08 09:25:56 +00:00
752ebd47cb
- Snapshot all four versioned docs sections at v6.1.0; master continues to serve as "Next" (lastVersion: current, banner: unreleased) so editing master keeps updating the canonical URLs - Enable the previously-disabled components plugin and version it - Rename stale "developer_portal" references to "developer_docs" across package.json scripts, manage-versions.mjs, theme files (DocVersionBadge, DocVersionBanner), DOCS_CLAUDE.md, and README.md (URL backward-compat redirect /developer_portal/* preserved) - Add admin_docs version scripts; drop dead "tutorials" plugin id from the version badge - Generalize fixVersionedImports in manage-versions.mjs to walk every section's snapshot and rewrite ../../src/ and ../../data/ imports, catching admin_docs and components files that previous version cuts would have broken - Remove orphan files: developer_portal_versions.json, tutorials_versions.json, and stray empty versions.json files inside components/ and developer_docs/ content directories
2.1 KiB
2.1 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| Deployment | 7 |
Deployment
Once an extension has been developed, the deployment process involves packaging and uploading it to the host application.
Packaging is handled by the superset-extensions bundle command, which:
- Builds frontend assets using Webpack (with Module Federation configuration).
- Collects backend Python source files and all necessary resources.
- Generates a
manifest.jsonwith build-time metadata, including the contents ofextension.jsonand references to built assets. - Packages everything into a
.supxfile (a zip archive with a specific structure required by Superset).
To deploy an extension, place the .supx file in the extensions directory configured via EXTENSIONS_PATH in your superset_config.py:
EXTENSIONS_PATH = "/path/to/extensions"
During application startup, Superset automatically discovers and loads all .supx files from this directory:
- Scans the configured directory for
.supxfiles. - Validates each file is a properly formatted zip archive.
- Extracts and validates the extension manifest and metadata.
- Loads the extension, making it available for use.
This file-based approach simplifies deployment in containerized environments and enables version control of extensions alongside infrastructure configuration.