From b3bc1c085db497ffdafa3fdcb67eec85bd5bb40f Mon Sep 17 00:00:00 2001 From: Jonathan Cobb Date: Mon, 23 Nov 2020 12:54:27 -0500 Subject: [PATCH] update docs --- docs/launch-types.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/launch-types.md b/docs/launch-types.md index 08a990a1..7bb6241a 100644 --- a/docs/launch-types.md +++ b/docs/launch-types.md @@ -29,13 +29,11 @@ You don't connect devices to a sage/launcher. You just launcher other Bubbles wi A `node`, also often just called a Bubble, is a regular Bubble that acts as a VPN and you connect devices to it. ### Cloud Services -A Bubble can either delegate cloud services back to the launcher that created it, -or use the cloud services directly itself. +A Bubble can either delegate cloud services back to the launcher that created it (a "cloud Bubble"), +or use the cloud services directly itself (a "standalone Bubble"). - * When a Bubble delegates cloud services back to the Bubble that launched it, we call this a Bubble in cloud mode. - * When a Bubble calls cloud services directly, we call this a Bubble in standalone mode. +What are the pros/cons of each approach? -What are the upsides/downsides of each approach? If you don't want your cloud credentials stored in your node, use delegated cloud services. Alternatively, if you're starting a launcher or don't want cloud services mediated via a launcher, you'll want your Bubble to call cloud services directly.