-
Notifications
You must be signed in to change notification settings - Fork 3
Create subdomain for superset dashboard #7
Comments
If possible, I'd love to revisit this, thinking about |
Didn't realize that superset was just a full python app -- could we just migrate to heroku app, and copy this (with updates)? |
@patcon ive tried deploying to heroku a few months back, was struggling with some annoying errors wasn't successful. The current instance is on a EDGI gcp vm. |
Cool. Aside from db credentials, any config files you could paste or share in a gist, in case I want to take a stab at it? |
nope no special config files it just works out of the box. I think there is an option for migrating dashboards, if its deployed on heroku then can migrate all existing dashboard and slices. FYI Airbnb is no longer supporting superset, Apache has taken over so the docs have moved over there https://github.com/apache/incubator-superset |
Just pinging @titaniumbones here, can we look at deploying to Compute Canada VM? |
Also @b5 controls DNS so would be responsible for subdomain |
Perf, thanks all! Not working yet, but heroku-backed instance setup is here: Also started stubbing out a service access inventory doc for DataTogether, and heroku app is in there: Can anyone drop a quick run-down on the backends we need to support, so someone can prep heroku? https://superset.incubator.apache.org/installation.html#database-dependencies |
Re: Compute Canada VM's
I have a strong preference for Heroku for ease and stability of toolset, if it's a component that we don't expect to ever require a paid dyno (which I think this is). Of course, i will always try to hold my stront convictions loosely, so I'm down to discuss tonight :) EDIT: Then again, this one isn't changing much, as config is via UI, not in code. but i am reeeeeaaaally partial to Heroku, as I can just give access to new people via |
Also, the heroku instance is now working, but needs to be configured. If anyone is down, drop a msg or ping me in slack and I'll provision you an admin user! |
Hey @b5, if you felt like pointing a subdomain at the app, I'm happy to do the CLI setup afterwards: (you're collab on app, but might need owner privs. If you can, feel free to do whole thing!)
@b5 fwiw, just realize I'm not 100% on what data sources you were thinking for this. Care to expound? |
have migrated the dashboard from the GCP superset to the heroku one. https://datatogether-superset.herokuapp.com/superset/dashboard/archivers/ Feel free to shutdown the GCP superset instance |
Re: #6
Would be rad to consider this an official resource. Can @titaniumbones give it a subdomain? (Not suggesting anything fancy like proxying to a clean subdomain or anything -- keeping the subpaths seems fine for now.)
If superset can have multiple backends, we could just use one subdomain (and not worry about considering a namespacing for both the v1 and v2 dashboard.
Possibilities
dashboard.archivers.space
metrics.archivers.space
stats.archivers.space
(Defer to @b5 who understands terms that aren't taken yet in the design of archivers.space :) )
Technically, the superset instance seems to have some other uses, but perhaps we could pass on that discussion for now.
cc: @titaniumbones @sonalranjit @b5
The text was updated successfully, but these errors were encountered: