mirror of
https://github.com/caddyserver/website.git
synced 2025-05-07 04:07:13 -04:00
58 lines
No EOL
3.4 KiB
JSON
58 lines
No EOL
3.4 KiB
JSON
[
|
||
{
|
||
"name": "First last",
|
||
"role": "9999x developer",
|
||
"org": "Bigcorp",
|
||
"picture": "https://pbs.twimg.com/profile_images/1624497316366528512/fBMXDuiZ_400x400.jpg",
|
||
"quote": "Caddy is cool.",
|
||
"link": "https://..."
|
||
},
|
||
{
|
||
"name": "Brad Warren",
|
||
"role": "Lead Engineer of Certbot",
|
||
"org": "Electronic Frontier Foundation (EFF)",
|
||
"picture": "https://sea1.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmw/144/7797_2.png",
|
||
"quote": "I think we should consider making Caddy the default ACME client recommendation. … It allows for better integration between the TLS server and the ACME management of those certificates. … [ACME clients with] Apache and NGINX are inherently more error prone and brittle than having the TLS server manage its certificates itself. … Caddy is written in a memory-safe language. Adoption of memory-safe programming languages is something that both ISRG and the broader computer security community have been encouraging more and more lately.",
|
||
"link": "https://community.letsencrypt.org/t/should-our-default-client-recommendation-be-caddy-if-not-why-not/199949?u=mholt"
|
||
},
|
||
{
|
||
"name": "Josh Aas",
|
||
"role": "Executive Director",
|
||
"org": "Let's Encrypt",
|
||
"picture": "https://sea1.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josh/144/10641_2.png",
|
||
"quote": "Caddy is impressive. This is what we want, setting up a secure website.",
|
||
"link": "https://www.youtube.com/watch?v=OE5UhQGg_Fo"
|
||
},
|
||
{
|
||
"name": "Stripe",
|
||
"role": "Global Leader of Fintech",
|
||
"quote": "With its extensible architecture and on-line config API, Caddy powers many of Stripe's internal systems."
|
||
},
|
||
{
|
||
"name": "Robert Melton",
|
||
"role": "Software Developer",
|
||
"quote": "Our client was in deep trouble: they were about to fail PCI compliance. We tossed Caddy in front hours before the deadline and went from 40 to 0 security errors in just minutes. … We have put over 1,000 domains on Caddy so far."
|
||
},
|
||
{
|
||
"username": "lost_RD",
|
||
"quote": "Every time I have a problem, google directs me to a \"mature\" Traefik-based solution that barely works, if at all. Then I come here and there's a Caddy solution that blows it out of the water. New plan for today then. ... It's a simple addition to an already-simple config. Traefik is complexity on complexity and a nightmare to debug.",
|
||
"link": "https://discord.com/channels/569842713239879680/569842713239879682/1161874875053527081"
|
||
},
|
||
{
|
||
"name": "Karim Naufal",
|
||
"role": "Tech founder",
|
||
"quote": "After working for 12 hours straight, unable to make Traefik work and almost going nuts, I switched to Caddy and was able to make it work in 3 lines of code, HTTPS included. Thank you Caddy team for this magically simple and awesome project."
|
||
},
|
||
{
|
||
"name": "Kenn White",
|
||
"role": "Security engineer",
|
||
"org": "Subcontractor, UK government",
|
||
"quote": "This is a brilliant piece of software. ... Even on first install, the defaults are sane. Truly, great work. … Seriously: Caddy makes it possible for hundreds of thousands of very needy folk to get treatment. It’s the backbone of vital systems used by local Doctors Without Borders and local government ministries."
|
||
},
|
||
{
|
||
"name": "John Resig",
|
||
"role": "Creator of jQuery",
|
||
"quote": "Caddy is pretty incredible. A 3-line config yields a fully A-rated SSL site. Trivial!",
|
||
"link": "https://twitter.com/jeresig/status/821768122017398785"
|
||
}
|
||
] |