Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with min
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
dotnet-maestro[bot] b4a07ec58a
Update dependencies from https://github.com/dotnet/arcade build 20230318.1 (#1559)
3 years ago
.config [master] Update dependencies from dotnet/arcade (#735) 5 years ago
.github Add `.github/fabricbot.json` (#1427) 4 years ago
.vscode fix launch path (#307) 6 years ago
build Add/use dotnet-format 6 years ago
docs Added a reference to the Tye VSCode extension (#1487) 3 years ago
eng Update dependencies from https://github.com/dotnet/arcade build 20230318.1 (#1559) 3 years ago
samples Merge pull request #1531 from dotnet/dependabot/npm_and_yarn/samples/apps-with-core-angular/MoviesApp/http-cache-semantics-4.1.1 3 years ago
src Fix Dapr extension services name not matching issue, Applications services name changed from capital letters to lower-case (#1335) 3 years ago
test Try 17.3.2 versions 3 years ago
.editorconfig Initial skeleton 6 years ago
.gitattributes add .gitattributes 6 years ago
.gitignore Tye should validate that service names are valid DNS names (#480) 6 years ago
.sscignore Opt out of NPM feed warnings in sample projects. (#1448) 3 years ago
CODE-OF-CONDUCT.md Link Code of Conduct (#293) 6 years ago
CONTRIBUTING.md Fix minor grammar issue (#616) 6 years ago
Directory.Build.props Add LICENSE.txt to NuGet packages. (#1188) 4 years ago
Directory.Build.targets Implement custom deserialization and validation logic (#294) 6 years ago
LICENSE.txt WIP 6 years ago
NOTICE.txt Update version of Kubernetes Client (#429) 6 years ago
NuGet.config CI fixes (#1233) 4 years ago
README.md Replace 'master' with 'main' in various files (#974) 5 years ago
activate.ps1 Fix tye init --force (#896) 5 years ago
activate.sh Rename tye to dtye (#311) 6 years ago
azure-pipelines.yml Update windows ci image names (#1469) 3 years ago
build.cmd WIP 6 years ago
build.sh Update developer guide 6 years ago
clean.cmd Use out-of-proc MSBuild evaluation (#674) 5 years ago
clean.ps1 Use out-of-proc MSBuild evaluation (#674) 5 years ago
clean.sh Use out-of-proc MSBuild evaluation (#674) 5 years ago
global.json Update dependencies from https://github.com/dotnet/arcade build 20230318.1 (#1559) 3 years ago
install-tye.cmd Add support for Azure Functions v4 (#1285) 4 years ago
install-tye.ps1 Add support for Azure Functions v4 (#1285) 4 years ago
install-tye.sh Add support for Azure Functions v4 (#1285) 4 years ago
remove-tye.cmd Add support for Azure Functions v4 (#1285) 4 years ago
remove-tye.sh Add support for Azure Functions v4 (#1285) 4 years ago
restore.cmd remove non-existing switch "-all" and "-nobuild" from restore.cmd when calling arcade ".\eng\common\Build.ps1" (#360) 6 years ago
restore.sh Fix restore.sh 6 years ago
startvs.cmd WIP 6 years ago
tye.sln Azure function support (#572) 6 years ago

README.md

Project Tye

Tye is a developer tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.

Tye can:

  • Simplify microservices development by making it easy to:
    • Run many services with one command
    • Use dependencies in containers
    • Discover addresses of other services using simple conventions
  • Deploy .NET applications to Kubernetes by:
    • Automatically containerizing .NET applications
    • Generating Kubernetes manifests with minimal knowledge or configuration
    • Using the same conventions as development to keep it consistent

Want to learn more? Check out our FAQ or documentation.

Current Status

Project Tye is an open source experiment at the moment. We are using this time to try radical ideas to improve microservices developer productivity and see what works.

We plan to do releases with new features roughly every 4 weeks.

For the duration of the experiment, consider every part of the tye experience to be volatile. We will frequently make additions and changes to features that seem polished. We welcome feedback from anyone who's willing to be an early-adopter with tye; the team wants to know what's working well, and what's missing to build a whole-package .NET microservices developer productivity suite.


Build Status

Getting Started

See the getting started instructions and tutorials here.

How to Engage, Contribute, and Give Feedback

Some of the best ways to contribute are to try things out, file issues, join in design conversations, and make pull-requests.

  • Download our latest daily builds
  • Try tutorials and working with your own projects
  • Log issues if you find problems, or if you have suggestions.
  • Log an issue if you have feedback you want to share with the team.

Check out the contributing page to see the best places to log issues and start discussions.

Thank you for trying out Project Tye! We highly encourage you to provide feedback to help us continue to improve the tool, so we would love to learn more about your experience. Please let us know what you think by filling out our survey.

Reporting security issues and bugs

Tye is an experimental project, and as such we expect all users to take responsibility for evaluating the security of their own applications.

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

.NET Foundation

Tye is a .NET Foundation project.

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.

General .NET OSS discussions: .NET Foundation forums