QT/superset2
1
0
Fork 0
mirror of https://github.com/apache/superset.git synced 2026-04-19 08:04:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: cleanup FAB update perms (#11155)

Browse Source 
* chore: Using cache factory method

* chore: Deprecate outdated FAB_UPDATE_PERMS information

Co-authored-by: John Bodley <john.bodley@airbnb.com>
This commit is contained in:
John Bodley
2020-10-07 08:33:41 -07:00
committed by GitHub
parent 32e174d4b8
commit 6e0d1b8409
4 changed files with 2 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/installation.rst
View File

@@ -276,23 +276,6 @@ server (`superset run` or `flask run`) is not intended for production use.
If not using gunicorn, you may want to disable the use of flask-compress
by setting `COMPRESS_REGISTER = False` in your `superset_config.py`
Flask-AppBuilder Permissions
----------------------------
By default, every time the Flask-AppBuilder (FAB) app is initialized the
permissions and views are added automatically to the backend and associated with
the ‘Admin’ role. The issue, however, is when you are running multiple concurrent
workers this creates a lot of contention and race conditions when defining
permissions and views.
To alleviate this issue, the automatic updating of permissions can be disabled
by setting `FAB_UPDATE_PERMS = False` (defaults to True).
In a production environment initialization could take on the following form:
superset init
gunicorn -w 10 ... superset:app
Configuration behind a load balancer
------------------------------------