-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hostname to the configuration parameters. #19
Labels
enhancement
New feature or request
Comments
What is the use case? depending on your router keeping |
Seb,
That is true for accessing the RPi locally, however if you have several
stations and you need to monitor them remotely all the hostnames are the
same.
One workaround is to change: the overlay to disable, reboot, change the
hostname, overlay to enable and reboot again ..
…On Thu, Jun 16, 2022 at 9:35 PM Sebastien Chaumontet < ***@***.***> wrote:
What is the use case?
depending on your router keeping ogn-receiver as hostname will allow you
to go directly to http://ogn-receiver:8080 same for other ports.
Changing the hostname will kill the standard way to access the receiver.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6DYZ2IFH65I5VQEYGFNU3VPN6YZANCNFSM5W4EOQQA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Angel Casado
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One small thing that it will be handy, it will be to add "hostname" to the configuration parameters (OGN-receiver.conf) the possibility to change the hostname, instead of the default of the ogn-receiver
The text was updated successfully, but these errors were encountered: