Change the .local hostname #109
Replies: 2 comments 2 replies
-
You can change the prefix (i.e. the balena part) by changing to the hostname you want in the docker-compose file: https://github.com/maggie0002/balena-device-ui/blob/4529f66320b1d8bff32cf6651ceafe2a5afd70a6/docker-compose.yml#L10 In terms of removing the You could use the public device URLs or your own system to expose the device via a public URL over the internet, and expose the device UI that way, but of course you are then adding in some extra hops to get to the device. Best option I have found to at least ease some of the .local issue, and is already in here, is when a user connects to the device via WiFi they are presented with a captive portal: The captive portal provides the URL to use (it updates itself based on what your hostname is set to), and the ability to hit the button to copy it out. This hopefully helps remove some friction on explaining to users what the URL should be. I suspect the next question people will have is whether the link can be clickable, but it only remains in the scope of the captive portal. So you could click it and then the captive portal window could load the UI, but there is no way to click it and tell your device to open the URL in your installed browser. For this reason we just made it not clickable. |
Beta Was this translation helpful? Give feedback.
-
Thanks! I'm fine keeping the ".local" but just wanted a way to change it to something other than balena.local. example: frog.local :) |
Beta Was this translation helpful? Give feedback.
-
This project is awesome and I am the biggest fan.
A question, is it possible to change the .local hostname to something custom other than balena.local? Is that hardcoded or does it exist in a configuration file somewhere?
Beta Was this translation helpful? Give feedback.
All reactions