evanphx

5 ms·

1.
by evanphx 2mo ago
The honest answer to your question about where the line is: it's when you start writing your own health checks, restart logic, and deployment orchestration on top of compose. That's the tipping point where you're maintaining
2.
by evanphx 5mo ago
If you're open, love to get your thoughts on https://miren.dev . We've doing similar things, but leaning into the small team aspects of these systems, along with giving folks an optional cloud tie in to help with auth,
3.
by evanphx 5mo ago
Are you doing that across a fleet of machines or just one?
4.
by evanphx 5mo ago
Totally, it's all about the primitives. I'm curious where exe.dev is gonna build on the the base, or just leave it up to folks to add all their own bespoke stuff to do containers, logs, etc. The last 20 years has given us a lot of
5.
by evanphx 1y ago
Agree and so I went looking and here is the reason: https://github.com/InitWare/InitWare/commit/3ee721035525dbb1... . They started with a specific version of systemd and have been mutating it since then, so th
6.
by evanphx 2y ago
Upon hearing this (and seeing the software that you've got listed on the website) I went and bought one. Looks great!
7.
by evanphx 5y ago
Hi, Evan Phoenix, Rubinius creator here. I just wanted to stop in and say thank you for this comment. It means a lot to me, even after all these years that Rubinius helped you out. I mentioned this on twitter as well ( https://twi
8.
Tokio: A Finagle inspired network application framework for Rust(medium.com)
7 points by evanphx 10y ago|0 comments
9.
Structured Logging – Part 1: What's the Big Deal(blog.current.sh)
2 points by evanphx 11y ago|0 comments
10.
Show HN: Auto-update Kubernetes service records in DNSimple(github.com)
2 points by evanphx 11y ago|0 comments
11.
Help us build the log management SaaS you want to use: current.sh(current.sh)
11 points by evanphx 11y ago|0 comments
12.
by evanphx 12y ago
It's very true that things like timeouts are done better within the client library. But Templar can combine timeouts with caching, allowing an API to appear to still be active and returning something even when it's just very slow.
13.
by evanphx 12y ago
That assumes nginx has the capability to do what Templar does and I don't believe that's true.
14.
by evanphx 12y ago
Templar does not do SSL termination because it does not terminate requests for your api. It's designed to mediate connections between you and any APIs that you use, protecting you against those APIs being unreliable.
15.
by evanphx 12y ago
Yup! That's on the todo list. Auto-caching, as I'm calling it, would figure out a how long to cache something for and then be able to later on use HEAD to check if the url in question has changed. That cache time could be as long
16.
by evanphx 12y ago
Thanks Veejay!
17.
by evanphx 12y ago
Templar is designed to be used within your own infrastructure on a trusted network, where you talk to it and it talks to the outside world. An attacker would have to be already within your private network, and if they were, they could obser
18.
by evanphx 12y ago
Ah! Ok, I got it. Feels like the right way to handle this is the allow a blacklist to be defined via config file, then applied as request, something like "X-Templar-Blacklist: internal". The list would be a set of ip ranges and th
19.
by evanphx 12y ago
Looking at that CPAN module, it wouldn't be hard at all to add a blacklist to Templar via a config file that is checked. The EC2 => EC2 issue is probably the biggest stumbling block to getting what you want. I'll have to invest
20.
by evanphx 12y ago
That's good point actually, I could see that happening. What is your concern about the url used? That they point at something a user is trying to coerce you to hit? If so, that could be a public IP too..
21.
by evanphx 12y ago
A great question. Nginx is not typically configured as a normal proxy but it can certainly do it. A difference is that Templar gives you control of options applied to each request differently rather than the same the same to all. From timeo
22.
by evanphx 12y ago
I agree, async responses are a great tool. It's a question of figuring out a good way of delivering them back to the client. Another option is a long poll endpoint within Templar that it can deliver a stream of responses on. AMQP is an
23.
by evanphx 12y ago
Fire-and-Forget is on the todo list. Since you're asking about it I'll bump it up. The later, Templar could have an option that tell it to only connect to public ips. Would that do it for ya?
24.
by evanphx 12y ago
Author here! That's certainly an interesting feature that could be added. I have on the future list to support sending responses back via AMQP. Your callback scheme isn't much different than that.
25.
Templar: A proxy to improve HTTP API interactions(github.com)
68 points by evanphx 12y ago|25 comments
26.
Vega: a distributed mailbox system(github.com)
2 points by evanphx 12y ago|0 comments
27.
by evanphx 12y ago
Thanks so much for the info Eli. For those that want to attend the service, do you have a time and location available? Or should they contact you to get that? I'd like to pass it along to people who have asked on twitter.
28.
by evanphx 12y ago
Thanks, fixed!
29.
by evanphx 12y ago
Monit is wining this discussion because their DMCA notice has caused the code not be visible, since anyone with both codebases could easily look at them and see that Inspeqtor is not a translation of the Monit code in any shape or form. Bec
30.
by evanphx 13y ago
Virtualization allows us to spin up new instances and migrate traffic to them. This means we can work entirely from chef and keep things clean. This is important for our volunteers to have a complete picture of an instance and to be able to

More ›