083a97f353
Implements two flavor of library support for service-discovery: - GetConnectionString (arbitrary strings) augmenting existing functionality already in asp.net core - GetServiceUri (uris) can be combined from a protocol/host/port triple See the **extensive** doc `service_discovery.md` that is filled out in this PR. That documents pretty much everything about how this works now. |
||
|---|---|---|
| .config | ||
| .github | ||
| .vscode | ||
| build | ||
| docs | ||
| eng | ||
| samples | ||
| src | ||
| test | ||
| .editorconfig | ||
| .gitignore | ||
| CODE-OF-CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| NuGet.config | ||
| README.md | ||
| activate.ps1 | ||
| activate.sh | ||
| azure-pipelines.yml | ||
| build.cmd | ||
| build.sh | ||
| global.json | ||
| restore.cmd | ||
| restore.sh | ||
| startvs.cmd | ||
| tye.sln | ||
README.md
Project Tye
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 minimal configuration.
What tye can do:
- Run multiple projects locally.
- Easily manage dependencies running containers.
- Automatically build Docker images by following .NET's conventions.
- Deploy applications to Kubernetes with minimal configuration.
- Make secret management and service discovery easy.
Current Status
Project Tye is an open source experiment that will last at least until Nov 2020. 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.
Getting Started
See the getting started instructions and tutorials here.
How to Engage, Contribute, and Give Feedback
If you want a low-spam way to follow what the team is doing. We post a status update approximately every 2 weeks. You can find the issue here. Use the Notifications button to subscribe. Only team-members can post on this issue, so it's a good way to get a digest of what's happening without having to read every conversation.
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.
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