-
Notifications
You must be signed in to change notification settings - Fork 97
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
[enhancement] Development and production user interfaces #924
Comments
The fastest and easiest way I see to do so, is forking and deploying your own forks, as I did for some of my PRs. By having a personal deployment, we're free to experiment and research without any limitation. The drawback is that it implies a cost for the cloud provider. Alternatively, we could imagine a I hope I understood the question right :) |
yea. i'm not going to find the time to setup my own qhub. i am thinking that there qhub.dev/alpha or qhub.dev/sandbox. these endpoints would deploy a different on a different endpoint that allows for experimentation on production data. in this conformation, early adopters can try out new features and fall back the blessed user interface when problems arise. |
We'll need to open an RFD to discuss the staging/production workflow. |
JLab 4 allows users to install extensions by conda environments and with the addition of jhub-apps this is now possible in Nebari. |
Description
Currently the user interface uses some tools that improve the user experience, but there are more we can add. it would be nice to try different lab extensions before putting the into production. I am proposing at least two user interface images: the current prod version and a work in progress environment that we can use to add new features and test.
Value/benefit
currently, we can't change the user experience without impacting everyone. another development image would give us the freedom to provide an enhanced user interface without effecting the current services. i'd like to experiment with some of the collaborative tools we serve with hourhaus
this request builds off of ideas in #903 with adding different user interfaces to the qhub experience.
The text was updated successfully, but these errors were encountered: