Best way to update Open Remote Versions

Services
1

I know this might be seen as a worthless question, but what would be the best method to update Open Remote from version OpenRemote Manager v1.14.0-snapshot to the latest one?

I have been working with a custom deployment, and changing several things that come from the template on Github. I would love to know if the moment I update it, everything is going to keep working like usual. I guess there is no way to know before doing it right?

Also, any advice to keep my changes without losing them? What kind of methods do you usually do?

2

By custom deployment I suppose you mean custom project.
There’s some documentation on how to do this: Release Management | OpenRemote Documentation

To know what would be working or not, you would need to check the release notes of all intermediate versions, we try to indicate any breaking changes.
As you’re coming from quite an older version, I would do upgrade one (minor, not patch) version at a time and test in-between.

If you do NOT set the OR_SETUP_RUN_ON_RESTART, it should keep the database intact.

1 Like
3

Thanks for the tips!

Also, I would love to know if I have been working on a external service for Open Remote, is it possible there would be not a single scenario I have to modify the code again from my service even if I update Open Remote to the latest version?

I mean, as long as the newest updates don’t change how connections work, my external service (in its own docker and all that stuff) should be working without problem right?

4

I mean, as long as the newest updates don’t change how connections work, my external service (in its own docker and all that stuff) should be working without problem right?

That is correct.

1 Like