|
@@ -12,11 +12,27 @@ In order to activate your Local Launcher, you'll need accounts and/or API keys f |
|
|
|
|
|
|
|
|
Have these account credentials handy. Be prepared to sign up for new accounts where needed. |
|
|
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. Complete the information on this page and submit the |
|
|
|
|
|
data. The Bubble Launcher will create an initial "root" account and other basic system configurations. |
|
|
|
|
|
|
|
|
|
|
|
## 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 |
|
|
## Activation Notes |
|
|
|
|
|
|
|
|
### Root User Name |
|
|
### Root User Name |
|
|
Do not change the name of the root user. Certain parts of the system have hardcoded references to "root" as the |
|
|
Do not change the name of the root user. Certain parts of the system have hardcoded references to "root" as the |
|
|
name of the admin user. |
|
|
name of the admin user. |
|
|
|
|
|
* For web-based activation, this is the `Username` field near the top. |
|
|
|
|
|
* For JSON-based activation, this is the `name` JSON element. |
|
|
|
|
|
|
|
|
### Required Clouds |
|
|
### Required Clouds |
|
|
You must define at least one cloud provider for each of these categories: |
|
|
You must define at least one cloud provider for each of these categories: |
|
@@ -25,23 +41,15 @@ You must define at least one cloud provider for each of these categories: |
|
|
* Compute (Vultr, DigitalOcean or Amazon EC2) (note EC2 support is WIP, Vultr and DigitalOcean are stable) |
|
|
* Compute (Vultr, DigitalOcean or Amazon EC2) (note EC2 support is WIP, Vultr and DigitalOcean are stable) |
|
|
|
|
|
|
|
|
### Initial Domain |
|
|
### Initial Domain |
|
|
The initial Domain you define during activation must be owned by you, and the DNS provider for this domain must be the |
|
|
|
|
|
one selected in the "DNS Provider" drop-down box. |
|
|
|
|
|
|
|
|
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. |
|
|
|
|
|
|
|
|
## Activate via Web UI |
|
|
|
|
|
The browser-based admin UI should be displaying an "Activate" page. Complete the information on this page and submit the |
|
|
|
|
|
data. The Bubble Launcher will create an initial "root" account and other basic system configurations. |
|
|
|
|
|
|
|
|
|
|
|
## 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 |
|
|
|
|
|
|
|
|
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 running the above, refresh the web page that opened when the server started. You should see a login page. |
|
|
|
|
|
|
|
|
## 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. |
|
|
You can now login as the admin user using the email address `root@local.local` and the password from your `activation.json` file. |