mirror of https://github.com/apache/superset.git synced 2026-05-22 08:15:36 +00:00

Files

Claude Code 4266d36cf4 docs: cut 6.1.0 versions for docs, admin_docs, developer_docs, components

Snapshots all four versioned Docusaurus sections at v6.1.0, cut from
master after the version-cutting tooling (#39837) and broken-internal-
links fixes (#40102) landed. Captures fresh auto-generated content and
freezes data dependencies so the historical snapshot stays correct.

Versioning behavior: lastVersion stays at current for every section,
so the canonical URLs (/docs/..., /admin-docs/..., /developer-docs/...,
/components/...) continue to render content from master. The current
version is consistently labeled "Next" with an unreleased banner, and
6.1.0 is a historical pin accessible only via its explicit version
segment.

Component playground: previously disabled: true in versions-config.json,
now enabled and versioned. The plugin block in docusaurus.config.ts
was already gated only by the disabled flag, so no other code changes
were needed to bring it back online.

Snapshot includes:
- All MDX content for the four sections.
- Auto-gen captured fresh: 74 database pages (engine spec metadata),
~1,800 API reference files (openapi.json), 59 component pages
(Storybook stories).
- Data imports frozen at cut time into snapshot-local _versioned_data/
dirs:
versioned_docs/version-6.1.0/_versioned_data/src/data/databases.json
(canonical 80-database diagnostics from master, preserved by the
generator's input-hash cache)
admin_docs_versioned_docs/version-6.1.0/_versioned_data/data/countries.json
admin_docs_versioned_docs/version-6.1.0/_versioned_data/static/feature-flags.json
developer_docs_versioned_docs/version-6.1.0/_versioned_data/static/data/components.json
- Import paths in deeply-nested files rewritten so they still resolve
from one directory deeper inside the snapshot.

Verified via full yarn build: exit 0, no broken links surfaced by
onBrokenLinks: throw. Anchor warnings present are pre-existing on
master (community#superset-community-calendar) and unrelated.

2026-05-14 13:55:27 -07:00

2.1 KiB

Raw Blame History

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.json with build-time metadata, including the contents of extension.json and references to built assets.
Packages everything into a .supx file (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 .supx files.
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.

2.1 KiB Raw Blame History

Deployment

2.1 KiB

Raw Blame History