The `tye build` command will build all of an application's project services into containers without deploying or pushing the containers remotely.
The `tye build` command will build all of an application's project services into containers without deploying or pushing the containers remotely.
This command is useful for testing that all projects successfully build.
@ -30,10 +30,22 @@ If a directory path is specified, `tye build` will default to using these files,
## Options
- `-i|--interactive`
Interactive mode.
- `--tags <tags>`
Filter the group of running services by tag.
- `-v|--verbosity <Debug|Info|Quiet>`
The verbosity of logs emitted by `tye build`. Defaults to Info.
- `-f|--framework <framework>`
The target framework hint to use for all cross-targeting projects with multiple TFMs. This value must be a valid target framework for each individual cross-targeting project. Non-crosstargeting projects will ignore this hint and the value TFM configured in tye.yaml will override this hint.
@ -27,7 +27,7 @@ The `tye deploy` command will deploy an application to Kubernetes. `tye deploy`
> :bulb: Use `kubectl config view --minify --output 'jsonpath={..namespace}'` to view the current namespace.
> :warning: The `tye deploy` command requires access to a remote container registry. Images will be tagged using the registry configured in `tye.yaml` (if present), or using a registry supplied interactively at the command line.
> :warning: The `tye deploy` command requires access to a remote container registry. Images will be tagged using the registry configured in `tye.yaml` (if present), or using a registry supplied interactively at the command line.
> :bulb: The `tye deploy` command uses Docker's credentials for pushing to the remote container registry. Make sure Docker is configured to push to your registry before running `tye deploy`.
@ -51,15 +51,23 @@ If a directory path is specified, `tye deploy` will default to using these files
Does an interactive deployment that will accept input for values that are required by default.
- `-v|--verbosity <Debug|Info|Quiet>`
The verbosity of logs emitted by `tye deploy`. Defaults to Info.
- `-n|--namespace`
Specifies the Kubernetes namespace for deployment. Overrides a namespace value set in `tye.yaml`.
- `-v|--verbosity <Debug|Info|Quiet>`
- `-f|--framework <framework>`
The verbosity of logs emitted by `tye deploy`. Defaults to Info.
The target framework hint to use for all cross-targeting projects with multiple TFMs. This value must be a valid target framework for each individual cross-targeting project. Non-crosstargeting projects will ignore this hint and the value TFM configured in tye.yaml will override this hint.
@ -16,7 +16,7 @@ The `tye push` command will build all of an application's project services into
This command is useful if you want to use Tye to containerize .NET projects and manage deployment separately.
> :warning: The `tye push` command requires access to a remote container registry. Images will be tagged using the registry configured in `tye.yaml` (if present), or using a registry supplied interactively at the command line.
> :warning: The `tye push` command requires access to a remote container registry. Images will be tagged using the registry configured in `tye.yaml` (if present), or using a registry supplied interactively at the command line.
> :bulb: The `tye push` command uses Docker's credentials for pushing to the remote container registry. Make sure Docker is configured to push to your registry before running `tye push`.
@ -42,6 +42,18 @@ If a directory path is specified, `tye push` will default to using these files,
The verbosity of logs emitted by `tye deploy`. Defaults to Info.
- `--tags <tags>`
Filter the group of running services by tag.
- `-f|--framework <framework>`
The target framework hint to use for all cross-targeting projects with multiple TFMs. This value must be a valid target framework for each individual cross-targeting project. Non-crosstargeting projects will ignore this hint and the value TFM configured in tye.yaml will override this hint.
@ -39,11 +39,11 @@ If a directory path is specified, `tye run` will default to using these files, i
The port to run the dashboard on. Defaults to port 8000 if not specified.
- `--logs`
- `--logs <logs>`
Write structured application logs to the specified log providers. Supported providers are console, elastic (Elasticsearch), ai (ApplicationInsights), seq.
- `--dtrace <logs>`
- `--dtrace <trace>`
Write distributed traces to the specified providers. Supported providers are zipkin.
@ -51,21 +51,37 @@ If a directory path is specified, `tye run` will default to using these files, i
Waits for debugger attach to service. Specify `*` to wait to attach to all services.
- `--docker`
Run projects as docker containers.
- `--dashboard`
Launch dashboard on run.
- `--watch`
Watches for file changes in all projects that are built by tye. Uses [`dotnet watch`](https://docs.microsoft.com/en-us/aspnet/core/tutorials/dotnet-watch?view=aspnetcore-3.1) to monitor for file changes.
- `-f|--framework <framework>`
The target framework hint to use for all cross-targeting projects with multiple TFMs. This value must be a valid target framework for each individual cross-targeting project. Non-crosstargeting projects will ignore this hint and the value TFM configured in tye.yaml will override this hint.
- `--tags <tags>`
Filter the group of running services by tag.
- `--verbosity <verbosity>`
Sets the output verbosity of the process.
Possible values are
Sets the output verbosity of the process.
Possible values are
* `debug` - display all logs that the process outputs
* `info` - display only informational logs
* `quiet` - display only warnings and errors
The default value is `info`
- `--watch`
Watches for file changes in all projects that are built by tye. Uses [`dotnet watch`](https://docs.microsoft.com/en-us/aspnet/core/tutorials/dotnet-watch?view=aspnetcore-3.1) to monitor for file changes.
John Luo
6 years ago
GitHub