Skip to content

Self-Hosted Superset instance does not seem supported (yet?) #22

@thiemonipro

Description

@thiemonipro

The documentation currently indicates in both the authentication guide and the installation guide
that sup! should work with self-hosted Superset instances. Based on the current source code and my local testing, this does not appear to be supported yet?

Could the documentation be adjusted to reflect the state of the implementation?
For example, the README
offers a bit more details, but perhaps it would be better if there is separate documentation for self hosted instances so we can track the progress/state of the feature easier. That might also make it easier to get people to contribute to it.

I may be missing some context as I am only familiar with self-hosted Superset deployments and have no experience with Preset.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions