Support other applications on the same domain

[benjiwolff]

What is the problem you are trying to solve with this feature?

Many home-server enthusiasts, like to host multiple applications on the same domain/IP-address and default port using a reverse proxy and path prefixes. This is currently not possible with homebox, as it is a statically generated Nuxt application, that is hosted at the root path "/".

What is the solution you are proposing?

I suggest prefixing all routes used by homebox (e.g. with "homebox"), so that it can be used out of the box in a reverse proxy setup. This could be a separate docker image.

What alternatives have you considered?

• Making the root path configurable:
  Since Nuxt requires the root path at build time, it is not straight-forward to make the root path configurable, especially when using the docker image.

Additional context

Here is a POC that assumes a reverse proxy setup that forwards traffic from route /homebox/* on the host to /* on the backend API port.
a4ebd49

Contributions

• I have searched through existing ideas in the discussions to check if this is a duplicate

[benjiwolff]

What are the reasons for deploying homebox as a statically hosted nuxt app?

If it was deployed on a Node server, the base path could easily be configured with an environment variable NUXT_APP_BASE_URL at runtime. On top of being configurable, it would probably also be a more stable solution.

[tankerkiller125]

It's actually served up by the golang API server as files, running it as a node server would require splitting the application into two different images, and complicate deployment.

[benjiwolff]

I am using a local DNS server now to achieve a similar effect with subdomains, so I no longer need explicit support from homebox for this.

[tonyaellie]

related: #322