readme: chrome port: explain what happens and avoid pronouns

Pronouns like I, we, .. are just confusing in docs, as it's never
clear who is actually meant, so lets please avoid that...

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/README.md b/README.md
index ce054bfde5bdb8f3a6ae34caab0f66b6f195a35a..a1db0f87fdd2367f2cfb0661c9eb34b8b2307f51 100644 (file)
--- a/README.md
+++ b/README.md
@@ -87,13 +87,13 @@ variable:
 
 Now you can start the web based build normally:
 
-$ flutter run -d chrome
-
-I personally prefer to run with a fixed port, so that I can access and reuse configuration:
-
 $ flutter run -d chrome --web-port=35000
 
 
+NOTE: without setting a fixed port flutter uses a random one, as chrome binds
+ certificate expections and local browser storage to a (protocol, host, port)
+ tuple, this means that we'd lose all saved settings etc. every time else
+
 ### Use reverse proxy to allow connections to PVE and the App over the same port
 
 Launch App in Chrome: