[BUG] Stop ability of starting stopped shared apps from JupyterHub interface

[aktech]

Context

Here is the scenario, when a user creates an app and it's stopped over time and an admin user, who can see the shared app clicks on the app, the user is redirected to JupyterHub's interface to start the app, which calls the jupyterhub API directly instead of going via jhub-apps service, which ends up with following:

• creating a jupyterlab as it uses the default spawner
• loses all the user_options set by jhub-apps
• Gets disappeared from the app launcher home as only the apps with users_options['jhub_app'] = True are shown in the app launcher home.

Stopped shared app should only be started from this interface

We need to somehow disable starting from the jupyterhub UI

Value and/or benefit

• Ability to only create app from one interface
• Consistency in app creation

Anything else?

No response

[krassowski]

Currently the user who sees such an app is unable to "Start" it from dropdown:

That Start would go post to /server/ endpoint which currently has no parameters so it does not allow to start a specifc server, just the default server of a given user:

jhub-apps/jhub_apps/service/routes.py

Lines 161 to 181 in de8dae6

	@router.post("/server")
	async def create_server(
	server: ServerCreation = Depends(Checker(ServerCreation)),
	thumbnail: typing.Optional[UploadFile] = File(None),
	user: User = Depends(get_current_user),
	):
	logger.info("Creating server", server_name=server.servername, user=user.name)
	server.user_options.thumbnail = await get_thumbnail_data_url(
	framework_name=server.user_options.framework, thumbnail=thumbnail
	)
	hub_client = HubClient()
	return hub_client.create_server(
	username=user.name,
	servername=server.servername,
	user_options=server.user_options,
	)
	@router.post("/server/")
	@router.post("/server/{server_name}")
	async def start_server(

I guess that once we implement the new parameter in /server/ we could then change the main card link to a programmatic call to /server and then only redirect to the link location once the server reports back as running. Does it sound like a good plan?