Hi! I've been exploring integrations with the ASGI mount. I keep hitting issues when trying more complex scenarios than the intro docs / examples.

It's hard to debug and introspect because a lot is bundled together, so I'm looking for some details:

• what is bundled via create_asgi_app() and what is required for the app to run? (e.g., do I need user_config_manager?)
• I found marimo._server.api.router.build_routes() but what is required / optional?
• handling file paths when mounting is challenging (cwd for launching the server vs. main app dir vs. marimo ASGI subapp dir vs. marimo notebook path)
• the redirect feature from create_redirect_to_slash() adds misdirection and should be opt-in
• one potential source of challenge is the marimo app bundles HTTP, Websockets, and static files routes, but they might have different mount requirements for the main app (e.g., middlewares, conflicting paths)

solution

have a "core" ASGI app or set of routes with minimal features (no middleware, no LSP, no redirect) for developers. This would be in addition to the current "full ASGI app" that's more user-friendly

I really tried fixing this myself, and I'm willing to contribute, but would require some guidance on how to approach it