| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
This was a due to a miscommunication in the caddy team.
|
|
|
|
|
| |
https://github.com/caddyserver/caddy/releases/tag/v2.7.5
diff: https://github.com/caddyserver/caddy/compare/v2.7.4...v2.7.5
|
|
|
|
|
| |
https://github.com/caddyserver/caddy/releases/tag/v2.7.4
diff: https://github.com/caddyserver/caddy/compare/v2.7.3...v2.7.4
|
|\
| |
| | |
xcaddy: 0.3.4 -> 0.3.5
|
| |
| |
| |
| |
| | |
https://github.com/caddyserver/xcaddy/releases/tag/v0.3.5
https://github.com/caddyserver/xcaddy/compare/v0.3.4...v0.3.5
|
|/
|
|
|
|
|
|
|
|
|
| |
2.7.0-2.7.2 have been skipped due to bugs in the release.
https://github.com/caddyserver/caddy/releases/tag/v2.7.3
https://github.com/caddyserver/caddy/releases/tag/v2.7.2
https://github.com/caddyserver/caddy/releases/tag/v2.7.1
https://github.com/caddyserver/caddy/releases/tag/v2.7.0
diff: https://github.com/caddyserver/caddy/compare/v2.6.4...v2.7.3
|
| |
|
| |
|
|
|
|
|
| |
https://github.com/caddyserver/xcaddy/releases/tag/v0.3.4
diff: https://github.com/caddyserver/xcaddy/compare/v0.3.3...v0.3.4
|
|
|
|
|
| |
https://github.com/caddyserver/xcaddy/releases/tag/v0.3.3
diff: https://github.com/caddyserver/xcaddy/compare/v0.3.2...v0.3.3
|
| |
|
| |
|
|
|
|
| |
https://github.com/caddyserver/caddy/releases/tag/v2.6.4
|
|
|
|
| |
https://github.com/caddyserver/caddy/releases/tag/v2.6.3
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream xcaddy uses the $HOME directory as the temp directory on Darwin
in order to fix an interesting bug.
In order to find version information for Caddy, it runs a command that
needs to operate on file system without "noexec" set, but Darwin's temp
directory has it set.
We can tolerate losing version information, since the alternative is
that xcaddy does not run on Darwin.
|
|
|
|
|
|
|
|
|
|
|
|
| |
A tool that can be used to build the Caddy webserver with plugins.
It functions as its own package manager and calls out to the network, so
it can't build Caddy in nixpkgs, but it's useful for environments that:
1. Do not need sandboxed and reproducible builds.
2. Pin Caddy and plugin versions when using the tool and trust it to be
a reproducible, fixed derivation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part of: https://github.com/NixOS/nixpkgs/issues/108938
meta = with stdenv.lib;
is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.
This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.
The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
|
|
|
|
| |
https://github.com/caddyserver/caddy/releases/tag/v2.3.0
|
| |
|
| |
|
| |
|
|
|
|
| |
https://github.com/caddyserver/caddy/releases/tag/v2.2.0
|
|
|
|
|
|
|
| |
main.go gets overwritten in order to build caddy with telemetry
disabled, but the global variable `run` got neglected, and this in turn
broke the test in caddy/main_test.go.
This commit fixes that, and build can now complete.
|
| |
|
| |
|
|
|
|
| |
Rename legacy v1 to `caddy1`
|
|
|
|
|
| |
derivations (#95092)
The buildGoModule infrastructure does not make use of goPackagePath it is a residue from buildGoPackage.
|
| |
|
|\
| |
| | |
buildGoModule packages: editorconfig fixes
|
| | |
|
|/ |
|