Last updated
Burla's CLI contains the following commands:
Install a self-hosted Burla instance in your Google Cloud project.
Authenticate your machine.
Open / login to the Burla dashboard in your default browser.
The global arg --help
can be placed after any command or command group to see CLI documentation.
burla install
Install a self-hosted Burla instance in your Google Cloud project.
Running burla install
multiple times will update the existing installation with the latest version.
Installs Burla inside the Google Cloud project that your is currently pointing to. For a more user-friendly installation guide see:
To view your current gcloud project run: gcloud config get project
To change your current gcloud project run: gcloud config set project <desired-project-id>
Have the installed ().
Be logged in to the ()
(gcloud auth login
& gcloud auth application-default login
)
Have a Google Cloud user account with at least the minimum required permissions to install Burla.
Or: Just run burla install
, if you're missing any permissions it will tell you which ones!
Here are three sets of permissions, each of which would authorize somebody to run burla install
:
Here is exactly what happens when burla install
is run:
burla install
prints the following:
burla login
Authenticates the current machine through a Google OAuth consent screen.
Allows you to call remote_parallel_map
on Burla deployments where you're authorized to do so.
This is used to ensure that only people you have explicitly authorized have access to your Burla instance.
This token is refreshed each time the burla login
or burla dashboard
authorization flow is completed.
burla dashboard
Launch and login to the Burla dashboard associated with your current Google Cloud project.
Allows you to call remote_parallel_map
and access the Burla dashboard in Burla deployments where you're authorized to do so.
The current project's Burla dashboard URL is discovered using the following command:
gcloud run services describe burla-main-service ...
When redirecting to this dashboard the client attaches an authentication cookie identifying the user to the dashboard. Only explicitly authorized users are allowed to view a Burla dashboard.
We encourage you to check out in the client for even more specific installation details.
Launches the "sign in with google" page in your default web browser. This gives our backend access to only your email and name according to your google account. See our to learn how we protect this information.
Once signed-in successfully, an auth-token is saved in the text file burla_credentials.json
. This file is stored in your operating system's recommended user data directory which is determined using the python library.
Runs the same OAuth authorization flow used in the burla login
command, but redirects the user to their current project's Burla dashboard, instead of the page.
Like the burla login
command, this command also updates local authorization credentials stored in burla_credentials.json
, see the documentation for more info on these credentials.
Questions? , or email jake@burla.dev. We're always happy to talk.