-
Notifications
You must be signed in to change notification settings - Fork 738
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
Autocert Support #867
Autocert Support #867
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good! a few changes to the config structure.
would this work with TURN as well? that'll be a huge simplification to automatically generate certificate for TURN/TLS
@@ -27,4 +27,4 @@ FROM alpine | |||
COPY --from=builder /workspace/livekit-server /livekit-server | |||
|
|||
# Run the binary. | |||
ENTRYPOINT ["/livekit-server"] | |||
ENTRYPOINT ["/bin/sh","-c","./livekit-server --config $CONFIG --node-ip $NODEIP >> /tmp/livekit.log 2>&1"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this test code? we do not want to modify our build script.
@@ -0,0 +1,19 @@ | |||
.MAIN: build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same for this file.
@@ -44,6 +44,7 @@ type Config struct { | |||
KeyFile string `yaml:"key_file,omitempty"` | |||
Keys map[string]string `yaml:"keys,omitempty"` | |||
Region string `yaml:"region,omitempty"` | |||
AutocertCache string `yaml:"autocert_cache,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not clear that this enables auto ssl, we'd also want to group this config with future configuration parameters such as using another provider than LetsEncrypt.
AutocertCache string `yaml:"autocert_cache,omitempty"` | |
AutoCert AutoCertConfig `yaml:"autocert"` |
Enabled bool
CacheDirectory string
``
Done.
#898
Thank you!
…On Sun, Aug 7, 2022 at 1:01 AM David Zhao ***@***.***> wrote:
***@***.**** commented on this pull request.
looks good! a few changes to the config structure.
would this work with TURN as well? that'll be a huge simplification to
automatically generate certificate for TURN/TLS
------------------------------
In Dockerfile
<#867 (comment)>:
> @@ -27,4 +27,4 @@ FROM alpine
COPY --from=builder /workspace/livekit-server /livekit-server
# Run the binary.
-ENTRYPOINT ["/livekit-server"]
+ENTRYPOINT ["/bin/sh","-c","./livekit-server --config $CONFIG --node-ip $NODEIP >> /tmp/livekit.log 2>&1"]
Is this test code? we do not want to modify our build script.
------------------------------
In Makefile
<#867 (comment)>:
> @@ -0,0 +1,19 @@
+.MAIN: build
same for this file.
------------------------------
In pkg/config/config.go
<#867 (comment)>:
> @@ -44,6 +44,7 @@ type Config struct {
KeyFile string `yaml:"key_file,omitempty"`
Keys map[string]string `yaml:"keys,omitempty"`
Region string `yaml:"region,omitempty"`
+ AutocertCache string `yaml:"autocert_cache,omitempty"`
It's not clear that this enables auto ssl, we'd also want to group this
config with future configuration parameters such as using another provider
than LetsEncrypt.
⬇️ Suggested change
- AutocertCache string `yaml:"autocert_cache,omitempty"`
+ AutoCert AutoCertConfig `yaml:"autocert"`
Enabled bool
CacheDirectory string
``
—
Reply to this email directly, view it on GitHub
<#867 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMZ7IE6Y2WJGZA374Q2A2TVX3OEVANCNFSM55OONKIQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Enabling an option to use Autocert Certificates
The option is ON, if config contains a line like
autocert_cache: /tmp/certs