What's the hosting architecture of the web client ?

[adam-devel]

Should I expect the web client to be hosted by vaultwarden ? or am I expected to host it with a simple file server ? or does it come with it's own dedicated server software ?

A file server seems too simple, and the use of nodejs suggests that the client uses a dedicated nodejs server, but when I try to go to the import page in the android client, it redirects me to {valwarden's address}/#/tools/import

the client expects the imprt tool (which is part of the webclient) to be hosted at the same location of the backend by the server.

so either, vaultwarden is expected to take care of hosting the web client (in which case, I would expect a location in which I am expected to put the server files), or I am expected to do some networking magic in order to forward some requests to vaultwarden and others (such as /toos/* to the sever hosting the webclient

TLDR: How does the hosting architecture look like ? I get different signals from different resources and I am struggling to reconcile them.

[BlackDex]

Checked the wiki already? https://github.com/dani-garcia/vaultwarden/wiki#supported-features

TLDR: Vaultwarden is an all-in-one system when using the container images. if not using container images, then some more steps are needed, for that, you need to check the documentation of those deployments.