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

Rename Machine into Node #115

Closed
juanfont opened this issue Sep 22, 2023 · 11 comments · Fixed by #132
Closed

Rename Machine into Node #115

juanfont opened this issue Sep 22, 2023 · 11 comments · Fixed by #132
Assignees
Labels

Comments

@juanfont
Copy link

Hi there,

Headscale maintainer here :)

FYI, we are renaming Machine into Node - to better fit the internal naming of Tailscale. This might impact this project.

You can track the status of the change here juanfont/headscale#1553

@routerino
Copy link
Contributor

Thanks for the heads up, I don't think that affects the UI as it's always been referring to machines as devices :).

Unless it affects the API at least. Any changes to the API will meet swift and decisive swearing updates to the UI.

@juanfont
Copy link
Author

juanfont commented Sep 23, 2023 via email

sponnusa added a commit to sponnusa/headscale-ui that referenced this issue Oct 4, 2023
Updated all the /machine API endpoints to /node
sponnusa added a commit to sponnusa/headscale-ui that referenced this issue Oct 4, 2023
Updated all the /machine API endpoints to /node
@sponnusa
Copy link

sponnusa commented Oct 4, 2023

Thanks @juanfont.

I've updated the API endpoints and it is working fine. Once the changes are verified, the pull request should be merged into the master.

@98h398hrpohpoai
Copy link

98h398hrpohpoai commented Nov 28, 2023

Noting for anyone that might encounter this that it's still broken in the current release file from January.
The api can be manually corrected by replacing "machine" with "node" in ./web/_app/immutable/chunks/apiFunctions-60f89b05.js

@jspin991513
Copy link

jspin991513 commented Dec 4, 2023

Unfortunately that's not the only file. Performing a grep turned up the following:
./_app/immutable/chunks/apiFunctions-60f89b05.js
./_app/immutable/components/pages/devices.html/_page.svelte-ad198750.js

It appears that there is some old logic for the /api/v1/routes path that needs some work.
I'm still looking into it....

@jspin991513
Copy link

Ok, it appears that /api/v1/node/1/routes no longer works.
Is this a bug?

@routerino
Copy link
Contributor

If you're trying to modify post-compiled svelte code you're going to have a bad time.

If you want to test headscale ui with the alpha headscale release, you will need to check out this branch and compile a release. Once the headscale release is in beta or RC I will start compiling beta releases.

@jspin991513
Copy link

If you're trying to modify post-compiled svelte code you're going to have a bad time.

If you want to test headscale ui with the alpha headscale release, you will need to check out this branch and compile a release. Once the headscale release is in beta or RC I will start compiling beta releases.

Thanks @routerino. It helps to do things right from the beginning.

@Hi-Timofey
Copy link

still got requests to /api/v1/machine from UI using latest docker image of headscale-ui. any updates on issue?

@routerino
Copy link
Contributor

still got requests to /api/v1/machine from UI using latest docker image of headscale-ui. any updates on issue?

Believe it or not, I'm not in the habit of creating a release that would break the production version of headscale to accommodate the alpha version.

All the current pull requests do not dynamically detect or account for both versions. I'll accept a pull request that does so, or make up one myself when it hits beta.

@Hi-Timofey
Copy link

still got requests to /api/v1/machine from UI using latest docker image of headscale-ui. any updates on issue?

Believe it or not, I'm not in the habit of creating a release that would break the production version of headscale to accommodate the alpha version.

All the current pull requests do not dynamically detect or account for both versions. I'll accept a pull request that does so, or make up one myself when it hits beta.

Had no idea if this beta or alpha, sorry. Docker hub just show version 23, but not the "alpha" mark. Will be w8ing for update.

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

Successfully merging a pull request may close this issue.

6 participants