-
Notifications
You must be signed in to change notification settings - Fork 0
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
So many questions! How do i run this? #17
Comments
? |
Binary1. Do i need to keep a service running to keep publishing a name? DockerDocker version this is just a wrapper around binary. This is the proper README that is needed and I'm not assume a low entry threshold level tbh. |
Hi @grishy, Thank you for taking the time to attempt to clarify things a little. I don't know why i though that you might be using some sort of nam register as it's all passed in as command arguments. I probably was confused with other libraries where some do use some storage and others (like yours) don't. If my above command example would have worked then it's clear how to use this. But, again, don't need it anymore :) (i just changed my name and went through the pain of updating some ESP32 devices with actual soldering (for TX/RX wires) ouch..). |
Hi,
Thank you for this project! It looks like what i need.
I essentially just need a network alias because some devices in my network know it by name X, some by name Y. Don't ask ;)
From the elaborate detailed description i "think" that this project does what i want it to do. But it's completely unclear to me how.
You have 2 ways to install. Binary and docker.
Binary
The binary version is partly clear to me. You register/publish new cnames.
What isn't clear here is:
Docker
The docker version is even more vague to me.
I'm looking forward to hearing some clarity about this. It's probably the fix for me :)
But as it is now, it's waaaaaay too vague for me to even try it.
The text was updated successfully, but these errors were encountered: