Address feedback from testing
Description
Going through the full setup from scratch after some time allowed me to notice some issues or items that could be improved, especially to reduce setup friction. This ticket is meant to allocate time in the upcoming sprint to address it and do another test.
Scope
Address or fix the following items, including answering questions and helping to test the updated code/instructions:
Setup
For easier tracking, items that have been moved elsewhere have been styled
strikethrough, with bold indicating more info
-
Authentication issue - I have been prompted to dodocker login registry.gitlab.com
with a personal token. Is that right, and could we avoid the need to login, ie allow anonymous access? -
Options missing in the official documentation that were helpful during setup:Using clean forced rebuilds when updating/changing the version:--force-recreate
Raw output display for debugging: BUILDKIT_PROGRESS=plain- Will be done in #320
-
Map builds:-
To avoid inflating the build command line, could we move the options to specify continents/countries to build to the.env
config file, defaulting to the country from the reverse IP lookup if not set?- Added to #163 scope
-
Can we also schedule a follow-up task to support all countries?- Created #355 for post-POC
-
-
Raspberry pi install - some commands to add to the setup instructions:sudo apt-get update && sudo apt dist-upgrade
-
sudo apt install jq
for the "extra command to get wifi to work on on Raspberry pi 3+- This will be obsolete after #163
-
Move README setup instructions sections about docker & git lfs install to the bottom of the page, after the device setup (those steps have to be done on the raspberry)- Will be done in #320
-
Could we change the default wifi password on the whitebox wifi to bewhitebox
rather than12345678
? That would match the ssh password - I bumped into the difference a few times, having to remember which is which.- Will be done in #163
Adding a device
-
The tutorial videos of steps 3 & 4 are the wrong ones (repeat video 2) - they need to be the ones which show how to do those 2 stepsAlso need to briefly explain the steps to go get the wifi details- Will be done in #346
-
"Skip" button next to "Add device" on the "Let's get you setup" page should be "Close" (since it's shown also after adding devices)- Will be done in #346
-
Testing on main from today, after adding my insta360 and entering its wifi details, it remains disconnected and red. Is it because it is still missing the work from !167 (merged) to be merged ot work on main, or should it already work?- Should be fixed inmain
by now- In any case, could we add debugging steps for those cases to the documentation, and link to this from the status message when it isn't able to connect?
- Looks like we should include the instructions from !153 (merged) in the documentation, too
Other issues
-
Some airplanes shown at coordinates 0,0 -- this could be the traffic shown by stratux as " Basic Mode S and No-Position Messages " in the web traffic admin?- Will be fixed in #290
Tablet
-
On tablet (Android + Firefox) it seem to work fine overall from some quick testing, but one recurring issue: after a minute or so the traffic would disappear (still there in Stratux) and I would have to refresh the page for it to come back- Created #360
Prod
-
Is it supported? I have only tested on dev so far - we should do the airplane test on production- Prod can now be tested after !169 (merged) was merged