hey there,
i did playing around with certmgr and cfssl to build internal CA for my homelab, and my first impression is : wow, what great toolset!
but i got a bit confusing while reading docs and making own experience with certmgr.
Can anybody explain how to build the binary of certmgr with go tools?! i am using golang 1.18.2.
go get is deprecated and replaced by go install. but go install github.com/cloudflare/certmgr/cmd/...@latest only build version 1.6.5 how to see here.
since i am using the newest version, the "ca" key in my specs.json works fine and a deprecated info will show if i use the "ca" setting under "authority" like here:
|
"file": { |
|
"path": "/etc/myservice/ca.pem", |
|
"owner": "www-data", |
|
"group": "www-data" |
|
}, |
so is there a reason why it still in readme.md at the newest version?!
it confused me while get started with this really nice peace of application.
i think the docs thing is not much important, but how to build can help me and other people a lot. hoping for a short explanation.
Chris
hey there,
i did playing around with certmgr and cfssl to build internal CA for my homelab, and my first impression is : wow, what great toolset!
but i got a bit confusing while reading docs and making own experience with certmgr.
Can anybody explain how to build the binary of certmgr with go tools?! i am using golang 1.18.2.
go getis deprecated and replaced bygo install. butgo install github.com/cloudflare/certmgr/cmd/...@latestonly build version 1.6.5 how to see here.since i am using the newest version, the "ca" key in my specs.json works fine and a deprecated info will show if i use the "ca" setting under "authority" like here:
certmgr/README.md
Lines 152 to 156 in 4af0d77
so is there a reason why it still in readme.md at the newest version?!
it confused me while get started with this really nice peace of application.
i think the docs thing is not much important, but how to build can help me and other people a lot. hoping for a short explanation.
Chris