Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to create a completely fresh reinstall of Superset #8844

Closed
metaperl opened this issue Dec 16, 2019 · 3 comments
Closed

Document how to create a completely fresh reinstall of Superset #8844

metaperl opened this issue Dec 16, 2019 · 3 comments
Labels
enhancement:request Enhancement request submitted by anyone from the community inactive Inactive for >= 30 days

Comments

@metaperl
Copy link

Here we read:

create a clean/new virtualenv and reinstall superset and dependencies

without a link to anywhere in the docs stating how to reinstall superset and erase any previous install. for instance, the database in $HOME/.superset/superset.db needs to be removed for a new installation to truly work.

reinstalling superset without doing so will create database clashes when you attempt to create the admin user.

@issue-label-bot issue-label-bot bot added the enhancement:request Enhancement request submitted by anyone from the community label Dec 16, 2019
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label #enhancement to this issue, with a confidence of 0.58. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@dpgaspar
Copy link
Member

Hi @metaperl,

The default database location is referenced here: https://superset.apache.org/installation.html#configuration

Don't know if updating the docs stating that user's can/should remove sqllite db on a reinstall is the right way to go, could further increase confusion around the process.

Yet, I'll update flask-appbuilder so that flask fab create-admin won't raise an exception if a user already exists

@stale
Copy link

stale bot commented Feb 16, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Feb 16, 2020
@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement:request Enhancement request submitted by anyone from the community inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

2 participants