Services
Commands that allow interacting with microservices in Beamable project
beam services [options]About
Commands that allow interacting with microservices in Beamable project
Options
| Name | Type | Description |
|---|---|---|
| --dryrun | Boolean | Should any networking happen? |
| --cid | String | Cid to use; will default to whatever is in the file system |
| --pid | String | Pid to use; will default to whatever is in the file system |
| --quiet | Boolean | When true, skip input waiting and use defaults |
| --host | String | The host endpoint for beamable |
| --refresh-token | String | Refresh token to use for the requests |
| --log | String | Extra logs gets printed out |
| --dir | String | Directory to use for configuration |
| --raw | Boolean | Output raw JSON to standard out. This happens by default when the command is being piped |
| --pretty | Boolean | Output syntax highlighted box text. This happens by default when the command is not piped |
| --dotnet-path | String | a custom location for dotnet |
| --version | Boolean | Show version information |
| --help | Boolean | Show help and usage information |
Sub Commands
services-deploy
services-get-connection-string
services-manifests
services-promote
services-ps
services-registry
services-reset
services-run
services-service-logs
services-service-metrics
services-stop
services-templates
services-upload-api
Updated 2 months ago
