Following our OAuth API improvements back in August, we’ve been able to make some changes to our command line tool to make it easier to use.
We now support public OAuth applications, which means you no longer have to create your own OAuth application credentials to use the CLI. It sounds a small change, but it makes configuring the CLI much less fiddly.
And while we were at it, we added a nicer interface for authenticating as a
user. Now you just use the login command to configure the CLI and and
authenticate:
$ sudo gem install brightbox-cli
Successfully installed brightbox-cli-2.3.2
$ brightbox login frances@example.com
Enter your password :And you’re ready to go:
$ brightbox servers
id status type zone created_on image_id cloud_ip_ids name
-------------------------------------------------------------------------------------------------
srv-ad13j active 4gb.ssd gb1-a 2015-05-25 img-md394 cip-a6prn web
srv-pd7nn active 2gb.ssd gb1-b 2015-09-05 img-dknew cip-ezmsd db
srv-tvnz8 active 2gb.ssd gb1-a 2015-10-15 img-ybh9i coreos
srv-n8jz7 active 1gb.ssd gb1-b 2015-10-21 img-bbm1e cip-oxlr2 benchtest
srv-bz02z active 1gb.ssd gb1-a 2015-11-02 img-bkqh0 leela (docker-machine)
srv-m1r07 active 1gb.ssd gb1-b 2015-11-02 img-bkqh0 fry (docker-machine)
-------------------------------------------------------------------------------------------------If you’re automating something, you’re still better sticking with API Clients rather than authenticating with your user credentials.
More details about installing and using the CLI in the getting started guide.
New to Brightbox? You can sign up in 2 minutes and start building servers, load balancers and SQL instances straight away. And you’ll get a £50 credit to get you started too.