241–247 of 247 posts
Earlier quoted context omitted.
There's no wsgi transport built-in, we haven't found any golang libraries that let us do this yet. For now, until we find a solution, we recommend using something like gunicorn and use the `reverse_proxy` directive in Caddy to proxy to it.
I'm no *SGI expert, but ASGI might be easier to bridge with the Golang-style concurrency-model than WSGI. Not sure if there are any libraries for go ASGI yet though.
Earlier quoted context omitted.
I'm no *SGI expert, but ASGI might be easier to bridge with the Golang-style concurrency-model than WSGI. Not sure if there are any libraries for go ASGI yet though.
A quick search is telling me no. https://www.google.com/search?q=golang+%22asgi%22
Earlier quoted context omitted.
I just contacted the maintainer and he let me know it should be ready to use in the coming days. Check back in a few days! :)
Thanks for asking. It's the only thing keeping me from switching over really.
Earlier quoted context omitted.
In comparison with other webservers it is slower. For me it's okay but metrics!
* Citation needed? (I mean, yes, of the thousands of dimensions of a web server, Caddy is not the fastest or leanest in all of them, but what's important to you?) Counterpoints: - https://twitter.com/mattiasgeniar/status/1249751608721911814 - https://twitter.com/JackEllis/status/1257396020662673414
How fast is this bad boi? Or are there any benchmarks I can look at? I can tell the sell here, isn't "fastest EVAR" but how fast is it? Or where is fucking righteous, and where is it horrible? I'm guessing it's doing okay since it's Regardless, looks super cool, and excited to give this a try. One last thing... great job on the website, seriously 11/10 for a developer/command-line tool. Clearly says it does, shows so…
Will there be a time when performance will be relevant for Caddy?