tsai/tye - tye - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
John Luo	9ca63ede34	Revert "Johluo/revert to 3.1 (#592 )" (#611 ) This reverts commit `ae9e3b317d`.	6 years ago
John Luo	ae9e3b317d	Johluo/revert to 3.1 (#592 )	6 years ago
Justin Kotalik	0e51ddbe2d	Add support for 5.0 and change sample to 5.0 (#585 ) * Add support for 5.0 and change sample to 5.0 * targetframeworkversion	6 years ago
Justin Kotalik	32d2214abc	Fix some metric on dashboard (#584 )	6 years ago
Justin Kotalik	379ff07b06	Azure function support (#572 )	6 years ago
Ryan Nowak	0e1f027816	Use W3C format in frontend-backend	6 years ago
Ryan Nowak	af5eef1929	Normalize line endings	6 years ago
Ryan Nowak	083a97f353	Implement library support for service discovery (#299 ) 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.	6 years ago
David Fowler	8ac8f93098	Add test for container -> host communication. (#290 ) * Add test for container -> host communication. * Small tweaks - Modify frontend-backend app to print backend url - Fix log in docker runner - Rename test to use docker instead of container * More clean up - Don't set container port if the service isn't a container * Bind to all interfaces on linux only	6 years ago
David Fowler	3e0d1f3941	We get proxying for free within the container (#288 ) - Turns out the same alias works fine and docker will associate multiple IPs with a single alias - Remove the docker run command from the output and leave it in the log - Dump out the backend host names in the frontend backend example	6 years ago
Ryan Nowak	d69009b730	Auto-assign ports when inferred from launch settings This tries to add some auto-detect magic to make common scenarios work without any extra configuration, which avoiding doing obtuse stuff. - We ignore the ports in launch settings (avoid conflict in the hello world multi-project case) - When we infer bindings based on launch settings we set them to auto-select a port - The user setting a port via tye.yaml will always win - Bindings that are not inferred from launch settings still work the same way (we don't auto-auto-select a port) - When we deploy we ignore https The HTTPS behavior might need discussion, but we haven't started looking at a recipe for HTTPs inside the cluster in k8s, and it's not clear whether we even want to. One could also make the argument that we should skip TLS locally because we're not doing it inside the cluster. Someone writing an app today that assumes TLS in their code (using https URLs, or gRPC + TLS) will have a non-trivial path to k8s for now anyway. So, skipping https bindings for k8s really just makes us more honest.	6 years ago
Justin Kotalik	19190e79b1	Add frontend-backend test (#89 )	6 years ago
Justin Kotalik	340fe5182d	Add license and headers (#74 )	6 years ago
Ryan Nowak	80106201a6	use a different port	6 years ago
Ryan Nowak	5edb70d901	Check in some yamlz and examplez	6 years ago
Ryan Nowak	2005215f9f	Simplify samples	6 years ago
Ryan Nowak	9c7e2a38a4	Add frontend/backend sample (works with tye run)	6 years ago

17 Commits (dev/ps/tryUpdateVersion)