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.
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.
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.
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
Do not change the name of the initial admin user, or some things might not work correctly.
Username
field near the top.name
JSON element.The username of the initial admin user should always be root
.
You must define at least one cloud provider for each of these categories:
The initial Domain you define during activation must be owned by you.
Domain Name
field near the bottom.domain.name
JSON element.The DNS provider for this domain must be specified.
DNS for this Domain
field at the bottom.domain.publicDns
JSON element.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.