-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failing on caddyserver.com #19
Build failing on caddyserver.com #19
Comments
@jimafisk , have you tried specifying the version in your download URL? |
@jimafisk , just tried downloading from caddyserver.com and it worked fine. |
i got the same problem i think ... i am guessing that the version of xcaddy has to match the version of the this repo in some way ???
|
i tried the 2 latest tagged versions of xcaddy at https://github.com/caddyserver/xcaddy/releases/tag/ both versions got the same error. |
i also tried the ''' make all ''' with the latest xcaddy just like the make file does. also fails... |
I get the same error as @gedw99 using Docker:
Throws the same error above. |
go-git stays at v5.4.2 due to backwards-incompatible breaking change. goimports is run to reformat the code. fixes greenpau#19 Co-authored-by: Thorsten Essig <[email protected]>
see: https://github.com/zuohuadong/caddy-git run:
|
Upgraded to the latest: https://github.com/greenpau/caddy-git/releases/tag/v1.0.8 |
Describe the issue
When I try to download Caddy with this plugin built in it hangs for a long time and ultimately fails: https://caddyserver.com/download?package=github.com%2Fgreenpau%2Fcaddy-git
Running a build with another plugin downloads a binary rather quickly without issue.
Is there a chance that this plugin isn't compatible with the latest version of Caddy? Do we have to build from source with a particular dependency that they can't provide through the website?
Configuration
N/A
Version Information
N/A
Expected behavior
I expect the binary with the plugin included to download.
Additional context
N/A
The text was updated successfully, but these errors were encountered: