Project Generate-env
[INTERNAL] Get the connection strings required to start a Microservice. This is used when running Standalone Microservices locally without Docker
beam project generate-env <service> <output> [options]
About
[INTERNAL] Get the connection strings required to start a Microservice. This is used when running Standalone Microservices locally without Docker
Arguments
| Name | Type | Description |
|---|---|---|
| service | ServiceName | Which service to generate the .env file for |
| output | String | Where to output the .env file |
Options
| Name | Type | Description |
|---|---|---|
| --include-prefix | Boolean | If true, the generated .env file will include the local machine name as prefix |
| --instance-count | Int32 | How many virtual websocket connections the server will open |
| --auto-deploy | Boolean | When enabled, automatically deploy dependencies that aren't running |
| --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 |
Parent Command
Updated about 2 months ago