After 10 months of combined efforts, the first beta for Caddy 2.5 is now available:
This is a huge milestone and we couldn’t have done it without your help, thank you. Please try it out and report any issues before we tag stable!
Caddy relies on sponsors
Did you know that I work on Caddy as my job? And now I support a family. If your company or its customers use Caddy, sponsorships are not only greatly appreciated, but also crucial to keeping the project going strong. There’s some great benefits available for your team as well!
Thank you to all current sponsors who make this possible, especially ZeroSSL (our executive sponsor). We look forward to serving you!
Right now the caddy upgrade command only upgrades to stable versions (would be a nice feature though) – so you’ll have to download from GitHub for the time being. Or use xcaddy.
INFO: Prepare Caddy...
DEBUG: Set custom Caddy binary path
INFO: Found custom Caddy at /share/caddy2/caddy
v2.5.0-beta.1 h1:lF5wWqqDJ6HjETbnBILvTAeKcThsz1+OeWB+d1tWxp4=
INFO: Prepare Caddyfile...
DEBUG: Set custom Caddyfile path
INFO: Caddyfile found at /share/caddy2/Caddyfile
INFO: Run Caddy...
Not sure why that is for you, I ran those commands just now (on my Macbook) and running strings ./x | grep v2.4.6 shows nothing, whereas strings ./x | grep v2.5.0 yields v2.5.0-beta.1. So it is definitely working
I have no idea. I just did what you did on my imac and I still get 2.4.6. But, I opened a browser and just downloaded the file and then I get 2.5.0 … so all good. Some reason curl isn’t getting the right file. Crazy. I will deploy it tomorrow on one of my linux servers. thanks everyone!
If your company or its customers use Caddy, sponsorships are not only greatly appreciated, but also crucial to keeping the project going strong. There’s some great benefits available for your team as well!
yes that’ll work.