News for hackers. Stuff that matters.

hairyhenderson

Re:Pyroscope and Grafana Phlare join together on Wednesday March 15, 2023 @02:56PM (#35173073)
What is "new" Grafana in this context? The only thing that sounds similar to this is the Grafana Image Renderer plugin, which uses Chromium. But that's hardly new (it's been around for about 4 years), and it's not part of core Grafana...
Re:Show HN: Caddy 2 on Monday May 04, 2020 @02:57PM (#23071886)
> It would be awesome if there were an official Caddy Builder docker image

You're in luck! :D

https://hub.docker.com/_/caddy

Note that the v2 images were _just_ pushed a few minutes ago, so the description might still point to rc3.

See "Adding custom Caddy modules" on that page for instructions on how to use the `caddy:builder` image.

Re:Show HN: Caddy 2 on Monday May 04, 2020 @02:19PM (#23071440)
Matt's already spoken to the ads/telemetry (which are ancient history).

My experience as a contributor has been nothing but positive. But if anyone's had a bad experience, I'm sure the Caddy team is more than willing to talk it out and reconcile.

Re:Show HN: Caddy 2 on Monday May 04, 2020 @01:49PM (#23071085)
Use Caddy wherever you'd otherwise use Apache HTTPD, nginx, IIS, traefik, Kong, etc...
Re:Why the MacBook Pro Is Limited to 16GB of RAM on Saturday November 19, 2016 @10:51PM (#12997162)
I doubt video editing would go very smoothly over an RDP connection to a Windows VM in the cloud ;)
Re:Build SSL HTTPS Website Using Docker on Saturday November 19, 2016 @10:39PM (#12997137)
nginx is cool and all, but IMO the best way to host an HTTPS site (with Docker or otherwise) is to use Caddy (https://caddyserver.com)
Re:Google Cloud is 50% cheaper than AWS on Saturday November 19, 2016 @10:26PM (#12997088)
"Anyone intending to be a serious user of AWS will use reservations."

Not in my experience... It's impossible to predict the kind of usage you're going to need over the next 1-3 years, especially when you're first getting started with AWS. If you underestimate, you waste money. If you overestimate, you waste even more money. Google's concept of "sustained use" discounts is _much_ more appealing to me.

Personally I'd make sure the various services were at least deployable as Docker containers. That way there's a lot of flexibility in switching providers, and makes it easier to deploy on prem later if/when you need to.

As for which platform? IMO the most important factor is which platforms the developer(s) are most comfortable/familiar with. The last thing a new SaaS startup needs is to waste time while the engineers figure out a new platform they've never used... Doesn't really matter how easy or cheap it is to deploy if there's no product ready to deploy ;)