Currently, updating upbrr requires maintaining the entire cloned GitHub repository on the host machine to pull changes and rebuild. For users running this in environments with strict storage limits—such as bare-metal Termux on Android—keeping the 200MB+ source folder just to facilitate future updates is highly inefficient. Once the final binary is compiled (e.g., to $PREFIX/bin/upbrr), the source code is otherwise useless.
It would be incredibly helpful to have a self-updating mechanism integrated directly into the compiled application. Ideally, this would take the form of an "Update" button within the Web UI. When a new release is pushed, the UI would notify the user, and clicking the button would automatically fetch and replace the active binary, restarting the app.
Currently, the only alternative is manually running a script to git pull and make build from the source directory, which forces users to permanently dedicate internal storage space to the repository and all of its node/go dependencies.
Other tools in the private tracker ecosystem, such as Jackett and NZBHydra2, handle this flawlessly. Their web interfaces manage the binary updates entirely internally, removing the need for the user to interface with the host OS or compiler to stay up to date.
Currently, updating upbrr requires maintaining the entire cloned GitHub repository on the host machine to pull changes and rebuild. For users running this in environments with strict storage limits—such as bare-metal Termux on Android—keeping the 200MB+ source folder just to facilitate future updates is highly inefficient. Once the final binary is compiled (e.g., to $PREFIX/bin/upbrr), the source code is otherwise useless.
It would be incredibly helpful to have a self-updating mechanism integrated directly into the compiled application. Ideally, this would take the form of an "Update" button within the Web UI. When a new release is pushed, the UI would notify the user, and clicking the button would automatically fetch and replace the active binary, restarting the app.
Currently, the only alternative is manually running a script to git pull and make build from the source directory, which forces users to permanently dedicate internal storage space to the repository and all of its node/go dependencies.
Other tools in the private tracker ecosystem, such as Jackett and NZBHydra2, handle this flawlessly. Their web interfaces manage the binary updates entirely internally, removing the need for the user to interface with the host OS or compiler to stay up to date.