Skip to content
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

Closed
markg85 opened this issue May 14, 2024 · 3 comments
Closed

So many questions! How do i run this? #17

markg85 opened this issue May 14, 2024 · 3 comments

Comments

@markg85
Copy link

markg85 commented May 14, 2024

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:

  1. Do i need to keep a service running to keep publishing a name?
  2. Do i need a systemd service file to run this in the background? And if so, what should i put in there?
  3. Where does it store those published names?
  4. How do i remove them if need be?

Docker
The docker version is even more vague to me.

  1. Nothing explains how i'd add a cname though the docker version. How?
  2. Where does docker store these?
  3. And how do i remove them?
  4. How do i even run the docker image (i know how to build/run a docker compose, this one is a little rhetorical where you should probably provide the steps to build/run it too)

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.

@grishy grishy closed this as completed Jul 8, 2024
@markg85
Copy link
Author

markg85 commented Jul 8, 2024

?

@grishy
Copy link
Owner

grishy commented Jul 9, 2024

Binary

1. Do i need to keep a service running to keep publishing a name?
Yes.
2. Do i need a systemd service file to run this in the background? And if so, what should i put in there?
Yes, if you want. Any way of running in bg is OK. This is up to you 👍
3. Where does it store those published names?
It just send commands to avahi-daemon. No internal store.
4. How do i remove them if need be?
Restart avahi-daemon or any way to drop cache when go-avahi-cname is not running.

Docker

Docker version this is just a wrapper around binary.
You can provide arguments as well as for binary version.
Don't need to build anything manually to run. Image already prepared.

This is the proper README that is needed and I'm not assume a low entry threshold level tbh.
Otherwise, there would be a lot of text. 😣

@markg85
Copy link
Author

markg85 commented Jul 9, 2024

Hi @grishy,

Thank you for taking the time to attempt to clarify things a little.
When i needed this (i don't need it anymore) i wanted to have one machine respond to both X.local and Y.local. With your explanation and re-reading your README i think a command like ./go-avahi-cname cname X.local. Y.local. running on the pc i want to be accessible by those names would've been my fix, would it not?

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..).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants