Why are we still debating the forum? What interests me is the original technical issue and a clear workaround.
Issue:
- Multiple venusOS instances in test and production. No (direct) access to latest 3.7 point release when Victron decides (on very short notice) to do a 3.6 beta. Therefore not able to plan our own roll-out schedule.
Possible workarounds:
- Keep an additional venusOS instance constantly updated on latest 3.7 and make a private copy of all updates.
- Put sd-cards in all other GX devices / venusOS instances, enable remote access to upload f/w of choice and do manual updates from sd-cards.
- Create a private library of updates and hack venusOS to point it toward that library
- A better way?
The whole point here is autonomy over our own roll-out agenda, independent of Victron’s development agenda.