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

[HELP]How to Automatically Monitor and Update Gateway Versions #1564

Open
DuXiaoChuang opened this issue Oct 21, 2024 · 3 comments
Open

[HELP]How to Automatically Monitor and Update Gateway Versions #1564

DuXiaoChuang opened this issue Oct 21, 2024 · 3 comments
Assignees

Comments

@DuXiaoChuang
Copy link

Describe the issue
How to Automatically Monitor and Update Gateway Versions,I see the updated URL in the code, but the URL cannot be opened, the error is as shown below. How should I build my own update website, please guide me, thank you

image

@yhliyr
Copy link
Contributor

yhliyr commented Oct 21, 2024

this url can only be request via POST method(as you can see in the TBUpdater.check_for_new_version() method in tb_updater.py), not via GET, such as by accessing the url in a browser

@DuXiaoChuang
Copy link
Author

this url can only be request via POST method(as you can see in the TBUpdater.check_for_new_version() method in tb_updater.py), not via GET, such as by accessing the url in a browser

How should I build my own update website, please guide me, thank you
image

@yhliyr
Copy link
Contributor

yhliyr commented Oct 22, 2024

From what I understand based on the code, the update process for Thingsboard-gateway is initiated by user sending RPC command from the platform(Thingsboard), the gateway receives the command and use 'pip install' to install the new version of the thingsboard-gateway python package and then reloads itself afterwards
So it depends on what kind of 'my own update website' you want

about the rpc command: #1459 (comment)

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

No branches or pull requests

4 participants