Here are some insights and suggestions I encountered while developing:
In seawater config highlight the different names of the cert (CA.pem & .pem files).
When rebar3 grisp pack - When packing a release, a green test instruction is displayed for non-rebar3 grisp-io plugin users. It could potentially distract users who don’t intend to perform the pack manually. Maybe we can write a warning.
Integrating all docu related to setup local dev, maybe in confluence:
-> 1) Ask for sys.config seawater env vars (api_key & password)
-> 2) Seawater create an account and add a subscription
--> 2,1) Explain subscription for testing in Seawater (and that you could use any token for subscription)
-> 3) Set up locally grisp_connect under grisp_project/_checkout/ with seawater
--> 3,1) Specify in 0 step where, like create a grisp project, and under _checkouts of grisp board project clone the necessary repos (like grisp_connect, rebar3_grisp, rebar3_grisp_io, grisp_updater_grisp2, etc).
Clarify persistent updates: Updates are stored persistently in memory, meaning users need to remove the SD card to boot from the partition. To avoid users restarting using removable.
Future idea) rebar3 configure --exisiting_project=<folder> just for things like integrate network a posteriori or Wi-Fi.
Tasks
Get partition state local test
Improvement and other ideas
Here are some insights and suggestions I encountered while developing:
In seawater config highlight the different names of the cert (CA.pem & .pem files).
When
rebar3 grisp pack
- When packing a release, a green test instruction is displayed for non-rebar3 grisp-io plugin users. It could potentially distract users who don’t intend to perform the pack manually. Maybe we can write a warning.Integrating all docu related to setup local dev, maybe in confluence: -> 1) Ask for sys.config seawater env vars (api_key & password) -> 2) Seawater create an account and add a subscription --> 2,1) Explain subscription for testing in Seawater (and that you could use any token for subscription) -> 3) Set up locally grisp_connect under grisp_project/_checkout/ with seawater --> 3,1) Specify in 0 step where, like create a grisp project, and under _checkouts of grisp board project clone the necessary repos (like grisp_connect, rebar3_grisp, rebar3_grisp_io, grisp_updater_grisp2, etc).
Clarify persistent updates: Updates are stored persistently in memory, meaning users need to remove the SD card to boot from the partition. To avoid users restarting using removable.
Future idea)
rebar3 configure --exisiting_project=<folder>
just for things like integrate network a posteriori or Wi-Fi.