admin UI app on different port?

Couldn't find this searching or under #246. Not sure if it is already asked/answered. It appears that currently vaultwarden serves everything on a single port (customizable via ROCKET_PORT [env]( It would be quite nice if the "admin" functions (API or otherwise) were able to be split off into a second server instance running on a different port (e.g. via ADMIN_PORT env). Example scenario... • running in [non-container]( mode • nginx providing SSL termination • don't want to expose admin features through firewall (e.g. access via tunnel to localhost only) • don't want to have to resort to path matching rules in nginx (e.g. special cases for /admin) and would rather just rely on port-based firewall rules. Maybe this doesn't make sense because the admin APIs are part of standard bitwarden protocol stuff that a client might use. But normally I prefer to put as little as necessary on public ports, so would be nice …