WedgeServer/wedge
View on GitHub ↗ ★ 239 Go
Fast, cross-platform HTTP/2 web server with automatic HTTPS
12 mentions on Hacker News by 11 people: 0 stories, 12 comments · first 2017-09-13 · latest 2025-10-23
20082026
-
Wait'll you hear about: - https://github.com/WedgeServer/wedge - https://github.com/tmpim/casket Both forks of Caddy...
comment by mholt · 2025-10-23 · in OpenMaxIO: Forked UI for MinIO Object Storage -
…There was also the Wedge fork which might have helped with the EOL but sadly it didn't go anywhere: https://github.com/WedgeServer/wedge > Despite v2 supporting a very similar config file, the documentation doesn't emphasise that and tries…
comment by KronisLV · 2023-05-24 · in Nginx 1.25.0: experimental HTTP/3 support -
…v2 is the only possibility nowadays, unless you want to maintain it yourself or like dead software: https://github.com/WedgeServer/wedge Of course, that's not a criticism of Caddy itself, just how we as an industry sometimes need rewrites…
comment by KronisLV · 2022-02-23 · in Avoiding the top Nginx configuration mistakes -
This is not the first contentious decision for caddy, and it does already have a fork: https://github.com/WedgeServer/wedge On top of that, "fast, automatic TLS HTTP2 capable web server" is not some complex feat in Go. HTTP2 is already…
comment by Vendan · 2018-04-30 · in Put a Fork in Caddy; It's Done -
…s.debian.org/cgi-bin/bugreport.cgi?bug=354622 [2]: https://news.ycombinator.com/item?id=15238315 [3]: https://github.com/WedgeServer/wedge/issues/2
comment by jlgaddis · 2017-09-16 · in The Realities of Being a FOSS Maintainer -
…a fork without the adware now, so the smart company will use the fork to get rid of the stupid ads. https://github.com/WedgeServer/wedge
comment by camus2 · 2017-09-14 · in Announcing Caddy Commercial Licenses -
> Second edit: Accusation of trademark violation within an hour of the fork, classy! https://github.com/WedgeServer/wedge/issues/2 This is just like Red Hat. He's put a lot of work into his product, whether free or not, so don't use…
comment by kbenson · 2017-09-13 · in Announcing Caddy Commercial Licenses -
…kept the project in the back of my mind. However, the responses from the Caddy folks here and at https://github.com/WedgeServer/wedge/issues/2 have been abysmal and without a clear change in course I'd feel embarrassed to recommend it to…
comment by kradle · 2017-09-13 · in Announcing Caddy Commercial Licenses -
Wedge. https://github.com/WedgeServer/wedge
comment by mattl · 2017-09-13 · in Announcing Caddy Commercial Licenses -
…like how one of the first contact bits from caddy to a fork of it is a thinly veiled legal threat: https://github.com/WedgeServer/wedge/issues/2
comment by xena · 2017-09-13 · in Announcing Caddy Commercial Licenses -
…I was thinking about switching from Nginx to Caddy but this news is nailing that door shut. [1] https://github.com/WedgeServer/wedge/issues/2
comment by ddevault · 2017-09-13 · in Announcing Caddy Commercial Licenses -
…obnoxious to the point of looking at NGINX Plus for commercial use instead. Edit: Here's my fork https://github.com/WedgeServer/wedge Second edit: Accusation of trademark violation within an hour of the fork, classy!…
comment by lol768 · 2017-09-13 · in Announcing Caddy Commercial Licenses