`enable_tls` panics

[lpil]

Hello!

This function panics, which a library should never do, especially not for simple configuration.

It is also not documented what the arguments are, or what happens when they are incorrect.

It seems strange to me that this API forces the programmer to keep the data on the file system, instead of passing it in as an argument like normal Gleam code.

Thanks,
Louis

[vshakitskiy]

Hello!

So, instead of passing file paths, we should provide the certificate and key values directly?

As for docs, yea, I will into documentation of everything I have, and make them more explanatory if needed. Thanks!

[lpil]

Passing them as bit arrays (or some other value) sounds good to me.

It would make error handling clearer for folks who keep this data on the file system, and remove some wasteful boilerplate and error handling for folks who store this data not on the filesystem. e.g. a secure secrets store, in memory as part of an ACME integration.

[vshakitskiy]

ewe is built on top of glisten and uses with_tls, which only takes files paths as arguments. There should be a change in glisten API in order to allow values directly.

[lpil]

Cool. I guess we make a PR! Assuming Alex is open to that. It could be a new function, to make it backwards compatible.