-
Updated
Nov 2, 2020 - Go
router
Here are 2,820 public repositories matching this topic...
-
Updated
Nov 2, 2020 - Go
-
Updated
Aug 17, 2020 - TypeScript
-
Updated
Oct 22, 2020 - Java
-
Updated
Oct 24, 2020 - JavaScript
-
Updated
Oct 27, 2020 - C++
-
Updated
Jun 28, 2020 - Python
-
Updated
Oct 11, 2020 - Go
-
Updated
Oct 15, 2020 - JavaScript
-
Updated
Sep 29, 2020 - TypeScript
-
Updated
Nov 3, 2020 - Go
-
Updated
Oct 25, 2020 - C++
-
Updated
Oct 5, 2020 - Go
-
Updated
Jul 30, 2020 - JavaScript
-
Updated
Oct 30, 2020 - Dart
-
Updated
Aug 9, 2020 - TypeScript
-
Updated
Dec 27, 2018 - Java
-
Updated
Sep 10, 2020 - JavaScript
-
Updated
Nov 1, 2020
I've configured Ingress with ALB using this: https://github.com/zalando-incubator/kube-ingress-aws-controller/tree/master/deploy
Given this rule for: Ingress
http:
paths:
- path: /
backend:
serviceName: app-web
servicePort: 443
and accessing my app over HTTPS using the: https://mydomain.app-web.example.com
my fin
Improve this page
Add a description, image, and links to the router topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the router topic, visit your repo's landing page and select "manage topics."
What problem does this feature solve?
It makes it possible to compare the latest route to START. Now you have to manually compare to ensure it's the same (or access START through the source, which I'd rather not).
Why do I want to compare with START? To check if this is the first routing made. Why would I want to do that? If coming from server-side and auth check fail, I want to replace th