瀏覽代碼

update docs

tags/v1.4.31
Jonathan Cobb 4 年之前
父節點
當前提交
b3bc1c085d
共有 1 個文件被更改,包括 3 次插入5 次删除
  1. +3
    -5
      docs/launch-types.md

+ 3
- 5
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.


Loading…
取消
儲存