Possible issue in Docker with hostname about backrest HOT 5 CLOSED

I tried to delete the host from the config file and restarting the container, but then no host is visible in the UI. Seems the host config is only created on the 1st run.
Changing the host on the config file requires the container to be restarted for the change to be visible on the interface.
So far, the only place to change the host name is the config file.

from backrest.

Hostname handling is mostly cosmetic at the moment. I'll leave this open to polish this up in future work but it's pretty low priority at the moment. I'm largely expecting it to be a useful feature for people running many deployments of backrest to tell at a glance which machine they've connected to.

from backrest.

First, I love backrest. I tried multiple other server-client backup programs and had limited success. Backrest/Restic 'just works.' Thank you!!!

In particular, it works great even when the network conditions aren't -- e.g. one spoke on spotty Wi-Fi, one on ethernet over powerline. Other programs timed out and/or failed in other ways.

So, I'm one of the people running multiple deployments. I had the same experience as OP. Agree it's no urgent issue. I have a hub-spoke setup with linux native install on the spokes. Works perfectly there. On my docker install, the UI says "backrest" no matter what I change the HOSTNAME var to in the docker compose file.

from backrest.

Hey, glad to hear it :)

Backrest populates the hostname into your config.json on first run. It's on the todo list to make it configurable in the UI but hasn't been high priority yet!

To update it, just edit the host property in your config and then restart backrest.

from backrest.

Adding an option to configure host name in the UI in the next release (exposed in settings).

from backrest.