update docs, make removal of peer manager more fault tolerant

bubble-server/src/main/resources/ansible/roles/finalizer/tasks/main.yml

@@ -27,7 +27,9 @@
 
 # Save 1% of memory, every bit counts on small nodes
 - name: Disable peer manager on small nodes
-  shell: bash -c "supervisorctl stop bubble_peer_manager && rm /etc/supervisor/conf.d/bubble_peer_manager.conf"
+  shell: |
+    supervisorctl stop bubble_peer_manager || echo 'Warning: error stopping bubble_peer_manager'
+    rm -f /etc/supervisor/conf.d/bubble_peer_manager.conf
   when: total_memory < 2048
 
 - name: save iptables v4 rules

bubble-server/src/main/resources/bubble-config.yml

@@ -96,7 +96,7 @@ releaseUrlBase: {{#exists BUBBLE_RELEASE_URL_BASE}}{{BUBBLE_RELEASE_URL_BASE}}{{
 disallowedCountries: {{DISALLOWED_COUNTRIES}}
 
 promoCodePolicy: {{#exists BUBBLE_PROMO_CODE_POLICY}}{{BUBBLE_PROMO_CODE_POLICY}}{{else}}disabled{{/exists}}
-requireSendMetrics: true
+requireSendMetrics: {{#exists BUBBLE_REQUIRE_SEND_METRICS}}{{BUBBLE_REQUIRE_SEND_METRICS}}{{else}}false{{/exists}}
 
 rateLimits:
   - { limit: 500, interval: 3s, block: 5m }

docs/launch-node-from-local.md

@@ -25,6 +25,15 @@ You should now see the advanced launch settings screen, like the one below:
 
 In the "Bubble Type" drop-down, ensure that "Fork Bubble" is selected.
 
+In the "Fork Host" field, enter the fully-qualified domain name (FQDN) that the Bubble will be known as.
+The FQDN has the form `host.net.domain`, where `host` and `net` identify the Bubble and can be whatever you
+want (at least 3 characters each), and `domain` is the domain that's been selected in the "Domain" field.
+
+For example, if you selected `example.com` in the "Domain" field, you could enter
+`foo.bar.example.com` as the Fork Host.
+
+You will also need to specify an admin email login -- it must be different than your current login.
+
 Choose your other configuration options, then click the "Launch Your Bubble!" button kick things off.
 
 The screen will refresh and show a progress meter, as in the screenshot below.
@@ -46,5 +55,8 @@ While your Bubble is launching, take a moment to
 [install the Bubble Native app](https://support.getbubblenow.com/hc/en-us/articles/360050801634-Connect-a-device-to-your-Bubble)
 on each device you plan on connecting to your Bubble.
 
-When your Bubble finishes launching, it will show a "Connect to Bubble" button. Click this and you'll be connected
-to your Bubble Node.
+When your Bubble finishes launching, you'll see something like the screenshot below.
+Click or tap "Connect to Bubble" to be connected to your new Bubble Node. You can then sign in.
+
+#### My Bubble Screen
+  <a href="img/my_bubble.png"><img src="img/my_bubble.png" alt="screenshot of My Bubble screen" height="500"/></a>

docs/launch-node-from-remote.md

@@ -53,5 +53,8 @@ While your Bubble is launching, take a moment to
 [install the Bubble Native app](https://support.getbubblenow.com/hc/en-us/articles/360050801634-Connect-a-device-to-your-Bubble)
 on each device you plan on connecting to your Bubble.
 
-When your Bubble finishes launching, it will show a "Connect to Bubble" button. Click this and you'll be connected
-to your Bubble Node.
+When your Bubble finishes launching, you'll see something like the screenshot below.
+Click or tap "Connect to Bubble" to be connected and automatically logged in to your new Bubble Node.
+
+#### My Bubble Screen
+  <a href="img/my_bubble.png"><img src="img/my_bubble.png" alt="screenshot of My Bubble screen" height="500"/></a>

docs/remote-launcher.md

@@ -37,10 +37,14 @@ You should now see the advanced launch settings screen, like the one below:
 In the "Bubble Type" drop-down box, ensure "Fork Launcher" is selected.
 
 In the "Fork Host" field, enter the fully-qualified domain name (FQDN) that the Bubble will be known as.
-This should end with whatever domain you have selected below in the "Domain" field.
+The FQDN has the form `host.net.domain`, where `host` and `net` identify the Bubble and can be whatever you
+want (at least 3 characters each), and `domain` is the domain that's been selected in the "Domain" field.
 
-In the "Plan" field, it is recommended to choose the highest-level plan. The Remote Launcher requires a decent amount
-of memory and CPU.
+For example, if you selected `example.com` in the "Domain" field, you could enter
+`foo.bar.example.com` as the Fork Host.
+
+In the "Plan" field, it is recommended to choose the highest-level plan.
+The Remote Launcher requires a decent amount of memory and CPU.
 
 In the "Domain" field, choose the domain that corresponds to the FQDN you entered in the "Fork Host" field.