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

11 Tags

20 MiB

Tree: 76df4e3f2b

Author	SHA1	Message	Date
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