RTM/sootie-dynamic-dns
0
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

add records for new server rtm-hazel #2

Open
jmakdah2 wants to merge 1 commits from add_hazel into main
pull from: add_hazel
merge into: RTM:main
Conversation 1 Commits 1 Files Changed 2 +44 -2
jmakdah2 commented 2026-05-17 21:09:26 +00:00
Owner
Copy Link
No description provided.
jmakdah2 added 1 commit 2026-05-17 21:09:26 +00:00
add records for new server rtm-hazel 2f25cc9bda
linnealovespie requested changes 2026-05-18 22:38:53 +00:00
headscale-records.json
@ -2,0 +20,4 @@
"value": "100.64.0.5"
},
{
"name": "layltta",
linnealovespie commented 2026-05-18 22:38:03 +00:00
Owner
Copy Link

is this typo leftover from before? Should be laylotta

is this typo leftover from before? Should be laylotta
👍 1
jmakdah2 commented 2026-05-19 18:22:25 +00:00
Author
Owner
Copy Link

looks like it was there before, i will fix that

looks like it was there before, i will fix that
headscale.py
@ -17,2 +17,3 @@
laylotta = Host("layltta", "100.64.0.7", ["laylotta.resisttechmonopolies.online"])
hosts = [sootie, mango, laylotta]
hazel = Host("rtm-hazel", "100.64.0.16", ["hazel.resisttechmonopolies.online"])
hosts = [sootie, mango, laylotta, rtm-hazel]
linnealovespie commented 2026-05-18 22:38:38 +00:00
Owner
Copy Link

rtm-hazel or hazel?

rtm-hazel or hazel?
👍 1
ammaratef45 commented 2026-05-19 07:21:05 +00:00
Owner
Copy Link

is this the same code generated the headscale-records.json with it? the generated host name is hazel but the code says rtm-hazel huh

is this the same code generated the headscale-records.json with it? the generated host name is hazel but the code says rtm-hazel huh
jmakdah2 commented 2026-05-19 18:24:40 +00:00
Author
Owner
Copy Link

The name of my vm is rtm-hazel (you will see that if looking on headscale connected devices). Oops, I need to change the variable name to rtm-hazel too.

but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead?

The name of my vm is rtm-hazel (you will see that if looking on headscale connected devices). Oops, I need to change the variable name to rtm-hazel too. but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead?
ammaratef45 commented 2026-05-19 19:23:28 +00:00
Owner
Copy Link

@jmakdah2

The name of my vm is rtm-hazel

So, that is the host name your vm is advertising for itself, head-scale automatically created a record for that that points to the right ip, here we can use different names and they would map to the correct ip. since your dns is hazel.xxxxx then the record here should also be hazel.xxxx

The goal is to have records that match what we have in cloudflare and eventually have deployments to this package automatically update cloudflare
note to slef: add a section in the readme to dictate that part

Speaking of the readme:

but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead?

https://git.coopcloud.tech/RTM/sootie-dynamic-dns/src/branch/main#headscale-records

The headscale-records.json is intended for be generated by running the headscale.py -- in the future this should be autogenerated on merge of a new commit and uploaded as a release artifact rather than a source tracked file(everytime I ask you to edit the same thing in multiple places ask me why; if the answer is not that we just didn't get the time to fix that then challenge me on it; having multiple places to change the same thing is a recipe for inconsistent records and impossibility of identifying the truth)
another note to self to explain this further in the readme

@jmakdah2 > The name of my vm is rtm-hazel So, that is the host name your vm is advertising for itself, head-scale automatically created a record for that that points to the right ip, here we can use different names and they would map to the correct ip. since your dns is hazel.xxxxx then the record here should also be hazel.xxxx The goal is to have records that match what we have in cloudflare and eventually have deployments to this package automatically update cloudflare note to slef: add a section in the readme to dictate that part Speaking of the readme: > but im not sure what you are referring to by generated code, i made these changes manually... is there somewhere i should be pulling this from headscale instead? https://git.coopcloud.tech/RTM/sootie-dynamic-dns/src/branch/main#headscale-records The headscale-records.json is intended for be generated by running the headscale.py -- in the future this should be autogenerated on merge of a new commit and uploaded as a release artifact rather than a source tracked file(everytime I ask you to edit the same thing in multiple places ask me why; if the answer is not that we just didn't get the time to fix that then challenge me on it; having multiple places to change the same thing is a recipe for inconsistent records and impossibility of identifying the truth) another note to self to explain this further in the readme
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin add_hazel:add_hazel
git checkout add_hazel
Sign in to join this conversation.
Reviewers
No Reviewers
linnealovespie
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
alu87 ammaratef45 brookechr jessib jjjj jmakdah2 jordansullivan kemcbride linnealovespie moosemower pathospothos twink182 Zigzagill
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RTM/sootie-dynamic-dns#2
No description provided.
Delete Branch "add_hazel"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?