The main Bubble source repository. Contains the Bubble API server, the web UI, documentation and utilities. https://getbubblenow.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

remote-launcher.md 2.2 KiB

пре 3 година
пре 4 година
пре 4 година
пре 4 година
пре 4 година
пре 4 година
пре 4 година
пре 4 година
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. Bubble Remote Launcher Mode
  2. ===========================
  3. You must already have a Bubble running in [Local Launcher Mode](local-launcher.md) to proceed.
  4. ## Start Bubble
  5. If your Bubble is not already running on your local system, start it by running `./bin/run.sh`
  6. ## Log In
  7. When your local Bubble finishes launching, it should open a web page. If you see a page with the title "Activation",
  8. then your Bubble still needs to be activated. Read about activation in the [Local Launcher Mode](local-launcher.md) instructions.
  9. If you see a login screen, you should be able to log in as the admin user using the email
  10. address `root@local.local` and the password from your `activation.json` file.
  11. ## Fork a Remote Launcher
  12. After you log in, you should see a "Launch Bubble" screen.
  13. If you don't see this screen, click the "My Bubble" link in the header.
  14. In the "Bubble Type" drop-down box, choose "Fork Launcher".
  15. In the "Fork Host" field, enter the fully-qualified domain name (FQDN) that the Bubble will be known as.
  16. In the "Plan" field, it is recommended to choose the highest-level plan. The Remote Launcher requires a decent amount
  17. of memory and CPU.
  18. In the "Domain" field, choose the domain that corresponds to the FQDN you entered in the "Fork Host" field.
  19. Configure the remaining fields as you desire. When you're ready, click the "Launch Your Bubble!" button.
  20. The screen will refresh and show a progress meter. A typical launch will take about 10 minutes.
  21. ## Your Very Remote Launcher
  22. The very first Remote Launcher you launch will build a [Packer](https://packer.io) image that will be used for this and
  23. subsequent launches.
  24. This process adds about 20-25 minutes to the launch process.
  25. While the packer image is building, the progress meter will appear to be "stuck" at 1%. This is normal.
  26. If you're curious, you can observe the packer image being built in your Bubble logs.
  27. This only happens the first time you launch a Remote Launcher.
  28. Later launches can skip this step, because Bubble will detect that the packer image already exists.
  29. ## Next Steps
  30. When your Bubble finishes launching, it will show a "Connect to Bubble" button. Click this and you'll be connected
  31. to your Remote Launcher.
  32. You are now ready to [Launch a Bubble](launch-node.md) from the Remote Launcher