Skip to content

Latest commit

 

History

History
64 lines (44 loc) · 2.42 KB

File metadata and controls

64 lines (44 loc) · 2.42 KB
title description lead date draft weight toc tags searchExtraKeywords resources
Getting started with BluBracket
How to sign up and start using BluBracket for free
2022-01-12 02:48:57 +0000
false
300
true
free trial
oauth
GitHub
Getting Started with BluBracket Team and Enterprise Editions - BluBracket
Getting Started with the Free Trial - BluBracket
src
three-step-process-sign-up.png
src
github-oauth.png
src
login-blubracket-page.png

Getting started with BluBracket is a three step process:

  1. Sign up
  2. Add a code server
  3. Start improving security

Signing up

{{< youtube _cgoY1YKs_w >}}

To start using BluBracket for free, visit our signup page and click the start for free button.

{{< figure src="three-step-process-sign-up.png" caption="Begin your three-step process by clicking the start for free button.">}}

Then approve the GitHub OAuth request.

{{< figure src="github-oauth.png" caption="Accept the GitHub OAuth request. ">}}

After authenticating and approving the permissions to sign in with GitHub, we'll create a free account for you.

Bookmark your account so you can come back easily.

Signing in

Refer to your welcome email when you first signed in to BluBracket for your personalized account dashboard URL. You must use this URL in order to sign in.

{{< figure src="login-blubracket-page.png" caption="BluBracket provides your login link through email." >}}

Adding your first code server

{{< youtube Ex-JA_xkZ0M >}}

Go to Settings → Code Servers in the BluBracket web console to add repos from your GitHub, GitLab, Bitbucket, or another supported code server.

Full details about how to add a code server are available in the usage guide.

Improve your code security with every commit

  1. Add BluBracket to your workflow with GitHub Checks or the CLI tool so you can identify risks before your next commit.
  2. Review existing risks to understand your overall code health and make a plan for what is urgent and what can wait.
  3. Track your security health improvements with every commit.

{{< youtube USPR40spmjY >}}