diff --git a/docs/launch-node-from-local.md b/docs/launch-node-from-local.md index 3dabe350..f0169119 100644 --- a/docs/launch-node-from-local.md +++ b/docs/launch-node-from-local.md @@ -22,30 +22,9 @@ The screen will refresh and show a progress meter. A typical launch will take ab The very first Bubble you launch will use a [packer image](packer.md) that was created during [activation](activation.md). -### Packer Image Creation -Normally the packer images are created during activation, and are generally available within about 20 minutes. - -If the required packer image is still being built when you launch your first Bubble, it's OK, -the launcher will wait for the packer image to be ready. - -If for some reason the packer image does not exist and is not currently being built, -then the launcher will start building the packer image right then. -This process adds about 20 minutes to the launch process. - -When launching a Bubble and the required packer image is still being built, -the progress meter will appear to be "stuck" at 1% until the image is ready. This is normal. - -If you're running the launcher from a [binary](run-binary.md) or [source](dev.md) Bubble distribution, -you can check the status of the packer jobs by running -```shell script -pack_status -``` - -If you're running the launcher from using the [Bubble Docker Launcher](docker-launcher.md), -you can observe output of the packer image being built in your Bubble logs. - -More details on packer and the `pack_status` command are available in -the [Bubble packer documentation](packer.md). +If the image is still being built or needs to be built, that will add some time to the launch process. + +The [Bubble packer documentation](packer.md) has more details on this process. ## Install Bubble Apps While your Bubble is launching, take a moment to diff --git a/docs/launch-node-from-remote.md b/docs/launch-node-from-remote.md index be043c06..d105dd71 100644 --- a/docs/launch-node-from-remote.md +++ b/docs/launch-node-from-remote.md @@ -21,16 +21,12 @@ Choose your configuration options, then click the "Launch Your Bubble!" button k The screen will refresh and show a progress meter. A typical launch will take about 10 minutes. ## Your Very First Bubble -The very first Bubble you launch will build a [Packer](https://packer.io) image that will be used for this and -subsequent launches. +The very first Bubble you launch will use a [packer image](packer.md) that was created +during [activation](activation.md). -This process adds about 20-25 minutes to the launch process. +If the image is still being built or needs to be built, that will add some time to the launch process. -While the packer image is building, the progress meter will appear to be "stuck" at 1%. This is normal. -If you're curious, you can observe the packer image being built in your Bubble logs. - -This only happens the first time you launch a Bubble. -Later launches can skip this step, because Bubble will detect that the packer image already exists. +The [Bubble packer documentation](packer.md) has more details on this process. ## Install Bubble Apps While your Bubble is launching, take a moment to diff --git a/docs/packer.md b/docs/packer.md index c95247ea..f185ffa2 100644 --- a/docs/packer.md +++ b/docs/packer.md @@ -23,13 +23,18 @@ A `node` image is for deploying new Bubbles in Node mode. A regular Bubble that Bubble will automatically use the appropriate image type based on the Launch Type. -To set the Launch Type: on the Bubble launch screen, click the "Launch with Advanced Settings" link. +### Setting the Launch Type +#### Via Web UI +On the Bubble launch screen, click the "Launch with Advanced Settings" link. +The first drop-down option is "Bubble Type". -When using the API, set the `launchType` property in the JSON request that creates the Bubble. +#### Via the API +When using the API, set the `launchType` property in the JSON object that creates the Bubble. ## Launching a Bubble while Packer Images are Building -If you try to launch a Bubble before the required packer image is ready, your Bubble launcher will detect that the image -is in the process of being built, and wait until it is ready before trying to use it. +If you try to launch a Bubble before the required packer image is ready, +your Bubble launcher will detect that the image is in the process of being built, +and wait until it is ready before trying to use it. ## Image Validity The packer images are tied to a specific Bubble version. As long as the Bubble API launcher can find packer images diff --git a/docs/remote-launcher.md b/docs/remote-launcher.md index b6a26e0c..d89377dd 100644 --- a/docs/remote-launcher.md +++ b/docs/remote-launcher.md @@ -30,16 +30,12 @@ Configure the remaining fields as you desire. When you're ready, click the "Laun The screen will refresh and show a progress meter. A typical launch will take about 10 minutes. ## Your Very Remote Launcher -The very first Remote Launcher you launch will build a [Packer](https://packer.io) image that will be used for this and -subsequent launches. +The very first Bubble Remote Launcher you launch will use a [packer image](packer.md) that was created +during [activation](activation.md). -This process adds about 20-25 minutes to the launch process. +If the image is still being built or needs to be built, that will add some time to the launch process. -While the packer image is building, the progress meter will appear to be "stuck" at 1%. This is normal. -If you're curious, you can observe the packer image being built in your Bubble logs. - -This only happens the first time you launch a Remote Launcher. -Later launches can skip this step, because Bubble will detect that the packer image already exists. +The [Bubble packer documentation](packer.md) has more details on this process. ## Next Steps When your Bubble finishes launching, it will show a "Connect to Bubble" button. Click this and you'll be connected