MISC issues with Nebari Deployment

[aktech]

Context

This is create a list of any MISC Fixes/Know issues

• Clicking on the Nebari logo on the top/left should take you to /hub/home and that should also be the default url when you go to nebari
• Remove JupyterLab from frameworks to avoid confusion
• After creating an app it redirects to the app url, which is sometimes 404, if app is taking a while to create (this needs some investigation)
• Add nitpicks to the front page theme to look similar to what it was looking previously
• Verify Start/Stop/Delete works as expected
• The service asks for authorization almost everytime, shouldn't be the case ideally.
• Fix deleting, when it's pending spawn

Anything else?

No response

[dharhas]

• conda-env list does not match between what jhub-apps dropdown thinks is available and what a user has available in Jupyter. i.e. I chose aktech-aktech-japps in the dropdown but I don't have permission for that env from my user in Jupyter etc.

[aktech]

conda-env list does not match between what jhub-apps dropdown thinks is available and what a user has available in Jupyter. i.e. I chose aktech-aktech-japps in the dropdown but I don't have permission for that env from my user in Jupyter etc.

Fix PR(s):

• JHub Apps: Filter conda envs by user nebari#2187
• Send user to conda env callable #55

[kcpevey]

I'd like a mechanism to manually, forcibly stop my server.

Usecase: When I launch VSCode, it will keep my server alive and prevent the idle culler from shutdown. To avoid this, I usually manually go to Hub Control Panel -> Shutdown Server. Since the Hub Control Panel no longer exists, I'd like a manual way to forcefully shut down my server.

Current workaround: Make sure you dont have VSCode open in a tab anywhere... Click "logout" in the jhub-apps landing page. Wait for the idle culler to shut down your instance.

I guess the other point here is that we are 100% reliant on the idle culler AND instances must remain open for that extra period of time (incurring costs)

[aktech]

@kcpevey Relevant PRs:

• Move JupyterLab under My Apps as Default App #63
• Remove JupyterLab from services list nebari#2189

[pavithraes]

Since we have VS Code listed as a "Service", the fact that this is opening through the same process as JupyterLab is currently hidden from end users.

So, we can "Stop" the VS Code service using the "JupyterLab" card under "My App", but it's not obvious to VS Code users to do this.

So we need some way to make this interaction clear, potential options:

• Move VSCode to My Apps, similar to JupyterLab with the option to Start, Stop, etc.
• In the "JupyterLab" card description, make a note that we can close VS Code instances from here as well
• Long term: I think we need to re-think the UX here - maybe the "Services" section can also have cards (similar to "My" Apps) - because moving JLab & VSCode to My Apps creates confusing terminology for what are "Services" and "Apps".