The Beamable CLI is a dotnet tool that allows developers to interact with Beamable via the CLI. It can be used to manage Beamable Content, Microservices, as well as make arbitrary requests to the Beamable backend.
You'll need to install Dotnet 6 before you can get started.
Verify it is installed by running
dotnet --version from a terminal.
To install the Beamable CLI, run the following commands in a shell.
dotnet tool install --global Beamable.Tools
And verify your installation with
As of 1.16.2, a globally installed CLI can manage its own updates through the use of the beam version install command.
The following command will install the latest CLI. The "latest" string can be any valid CLI version
beam version install latest
Check Versions on Nuget
Remember, Beamable.Tools is a dotnet tool available through Nuget. As such, you can find all available versions at nuget.org
If you have an existing organization, you should use beam init.
beam init --save-to-file
Don't forget the
--save-to-fileoption! By default, the CLI requires you pass authorization for each command you execute. If you don't want to do this, the
--save-to-fileoption will save your authorization information to the
./beamablefolder and reuse it for later requests. If you forgot to use this option, you can use the beam login command later.
This command will prompt you for your organization's alias, your credentials, and which realm to use. When it is complete, you should see a
./beamable folder in the current directory. See the Configuration for details about this folder. Now, you can run a beam config command to verify your project is set up.
You should expect to see your CID/PID printed out.
To check that everything is working correctly, you can use the beam me command. Now you have a configured CLI project!
Updated 4 months ago