The main Bubble source repository. Contains the Bubble API server, the web UI, documentation and utilities. https://getbubblenow.com
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
 
 
 
 

2.5 KiB

Bubble Activation

The very first time Bubble runs it has a blank database, nothing has been defined.

This is a Bubble that is awaiting activation.

Activation defines the initial data required to run a Bubble launcher. This includes the initial admin password, cloud services, and DNS domains.

Cloud Accounts

In order to activate your Local Launcher, you’ll need accounts and/or API keys from several cloud providers.

Have these account credentials handy. Be prepared to sign up for new accounts where needed.

Activate via Web UI

The browser-based admin UI should be displaying an “Activate” page.

Review the “Activation Notes” below, then complete the information on this page and press the “Activate” button to activate your Bubble Launcher.

Activate via command line

If you installed Bubble from a binary distribution or built it from source, you can also perform activation using the Bubble command line tools.

Make a copy of the file config/activation.json and edit the copy. There are comments in the file to guide you.

To activate your Local Launcher Bubble, run this command:

./bin/bactivate /path/to/activation.json

Activation Notes

Root User Name

Do not change the name of the root user, or some things might not work correctly.

  • For web-based activation, this is the Username field near the top.
  • For JSON-based activation, this is the name JSON element.

The username of the initial admin user should always be root.

Required Clouds

You must define at least one cloud provider for each of these categories:

  • DNS (Amazon Route53 or GoDaddy DNS)
  • Email (SMTP, SendGrid or Mailgun)
  • Compute (Vultr, DigitalOcean or Amazon EC2) (note EC2 support is WIP, Vultr and DigitalOcean are stable)

Initial Domain

The initial Domain you define during activation must be owned by you.

  • For web-based activation, this is the Domain Name field near the bottom.
  • For JSON-based activation, this is the domain.name JSON element.

The DNS provider for this domain must be specified.

  • For web-based activation, this is the DNS for this Domain field at the bottom.
  • For JSON-based activation, this is the domain.publicDns JSON element.

After Activating

After performing activation, refresh the web page that opened when the server started. You should see a login page.

You can now login as the admin user using the email address root@local.local and the password from your activation.json file.