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

Switch to dns names instead of IPs in compose files #313

Open
1 task done
jcvernaleo opened this issue Nov 8, 2024 · 2 comments
Open
1 task done

Switch to dns names instead of IPs in compose files #313

jcvernaleo opened this issue Nov 8, 2024 · 2 comments
Assignees
Labels
status: triage This is awaiting review. Maintainers should this label once triaged type: enhancement This improves existing functionality

Comments

@jcvernaleo
Copy link
Contributor

Confirmation

  • I have checked for similar issues.

Problem

No response

Suggested solution

title says it all

Additional Information

No response

@jcvernaleo jcvernaleo added status: triage This is awaiting review. Maintainers should this label once triaged type: enhancement This improves existing functionality labels Nov 8, 2024
@ClaytonNorthey92
Copy link
Contributor

hey @jcvernaleo are you thinking of the op-node static peering in the compose files? I know that it uses the multiaddress spec (found here), I was having difficulty using dns names when I last worked on this, I can't remember exactly why. I will need to revisit.

@jcvernaleo
Copy link
Contributor Author

I think this had to do with static peering but I don't fully remember either.

If that turns out to be the wrong solution, feel free to close or adjust based on what makes the most sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: triage This is awaiting review. Maintainers should this label once triaged type: enhancement This improves existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants