Conversation
|
Thanks for the update @KoalaSat! I tested the upgrade and hit one compatibility issue: the new client serves HTTPS, while Umbrel’s app proxy still connects to it over HTTP, so the app fails to open. We have built-in HTTPS coming in umbrelOS 2.0, which is currently in beta, with the stable release scheduled for the 22nd. I think we can use that here by adding: manifestVersion: 2
requiresHttps: trueWe’d also configure RoboSats to serve HTTP internally and let Umbrel handle HTTPS for the browser. That should give OpenPGP 6 the secure context it needs and resolve the proxy mismatch. We could target this update for the 2.0 release and test the configuration, including robot creation and recovery, before going live. Does that sound okay to you? |
Sounds great, thank you! |
Type
App update
App
App ID: robosats
Upstream project: Robosats
Version: v0.8.7-alpha
Summary
Full changelog here: https://github.com/RoboSats/robosats/releases/tag/v0.8.7-alpha
Verification
Umbrel testing performed:
Environment tested:
Architecture tested:
Known lint warnings or caveats:
Notes
Permissions, dependencies, migrations, default credentials, or caveats:
For new apps, include screenshots and a logo reference. Umbrel will create the final App Store gallery assets.