Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
andydunstall
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
by
andydunstall
2y ago
From what I could see of FRP, it only runs a single server node so isn't suitable for production traffic (which needs to be fault tolerant, scale horizontally, support zero downtime deployments...) Piko is also designed to be easier to
2.
▲
by
andydunstall
2y ago
Few things: - If your trying to access a customer network (such as for BYOC), exposing a public port in the customer network is likely a no-go (or would require complex networking to setup VPC peering etc) - The Pico 'proxy' port
3.
▲
by
andydunstall
2y ago
As commented below, Pico is already a well established name for a text editor so I've renamed to Piko: https://github.com/andydunstall/piko
4.
▲
by
andydunstall
2y ago
Not yet (still quite a new project), its on the list to add one
5.
▲
by
andydunstall
2y ago
Yep I checked out overlay networks, its definitely a very cool project. However it also seems pretty complex to host. I think they are different use cases
6.
▲
by
andydunstall
2y ago
Could you elaborate? Do you mean tunnelling generally or this implementation?
7.
▲
by
andydunstall
2y ago
I didn't know there was already a long-established project called Pico :) As someone suggested below, I'll rename to 'Piko'
8.
▲
by
andydunstall
2y ago
Not sure I follow Pico is a reverse proxy, so the upstream services open outbound-only connections to Pico, then proxy clients send HTTP requests to Pico which are then routed to the upstream services So as long as your browser can access P
9.
▲
by
andydunstall
2y ago
Good idea - will do that!
10.
▲
by
andydunstall
2y ago
That demo only uses docker compose: https://github.com/andydunstall/pico/blob/main/docs/demo/doc...
11.
▲
by
andydunstall
2y ago
Yeah sorry I started Pico before realising...
12.
▲
by
andydunstall
2y ago
When Pico server nodes are replaced, the upstreams will automatically reconnect to a new node, then that node will propagate the new routing information to the other nodes in the cluster So if you have a single upstream for an endpoint, whe
13.
▲
Show HN: Pico: An open-source Ngrok alternative built for production traffic
(github.com)
244 points
by
andydunstall
2y ago
|
55 comments
14.
▲
by
andydunstall
2y ago
Very cool, I've been looking for an open source Ngrok alternative as well though for production traffic rather than development (I couldn't find a good option on awsome-tunneling so have been playing about with a proof of concept
15.
▲
Implementing TD-Gammon with Keras
(andrewdunstall.com)
1 points
by
andydunstall
5y ago
|
0 comments
16.
▲
by
andydunstall
5y ago
yep - as i mentioned in a comment below - we arn't concerned about when the key is actually deleted - only that its not returned when looked up if its TTL is hit sorry should have been more clear
17.
▲
by
andydunstall
5y ago
>The integrity of a set of related keys requires that either all keys exist, or none exist Sorry it wasent that clear that part of our fix was such that it no longer matters if all keys exist or none - we reordered the expires such that
18.
▲
by
andydunstall
5y ago
we reordered our keys such that they can expire at different times - also redis checks a keys TTL before returning - and wont return if its expired. i think it will 'eventually' delete if its not accessed, but we only cared about
19.
▲
by
andydunstall
5y ago
sorry i should have explained. by ordered i meant after expiring a key its TTL will be set, which will never be a time before a previous expire. when it looks up the key, if its TTL has been reached it will not be returned (which we checked
20.
▲
by
andydunstall
5y ago
thanks for pointing that out - will take a look :)
21.
▲
by
andydunstall
5y ago
yep good point :) - in the end it didnt matter much as we could maintain our invariants if we just reordered the expires
22.
▲
by
andydunstall
5y ago
yep - part of our fix was ordering the expires such that the invariants are maintained even if the expires arn't exactly at the same time (we are assuming expires are at least ordered)
23.
▲
by
andydunstall
5y ago
Hey, I'm the author of this blog post. Ask me anything!
24.
▲
Redis scripts do not expire keys atomically
(ably.com)
3 points
by
andydunstall
5y ago
|
0 comments