-
Notifications
You must be signed in to change notification settings - Fork 22
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
Trouble with latest adapter #2
Comments
I had a similar problem with no directives being recognized. Wrapping everthing in a As the README states this adapter is still work in progress, so it is to be expected that not all directives are working right now. |
Thanks for the report, and the tip/workaround! It's odd, all the docs I can find show the
And this page shows:
Indeed, this adapter is not yet complete. Contributions welcomed! This is a community project, so feel free to get involved. (Although @mohammed90 does seem to be having fun with it) |
I believe I've fixed it :) Can you check out the PR #3? It works for me now with the patch. |
That was hasty of me 😅 I've just tried with nginx to have the Is your config part of an |
It isn't, but perhaps I'm using an old version of nginx. In any case, I wrapped my
|
Great, sounds like there is no longer a problem then. 👍 Nice work, @mohammed90 ! Except for a few, the remaining directives will form a long tail that we can address in time. The SSL-related directives will need some special handling, after we decide whether to upgrade nginx's default logic (non-privacy-preserving, plaintext HTTP settings) to HTTPS, or to keep it the same, or make it configurable... |
I've tried building caddy with 09ce5f0 but I'm not getting the expected adapter behavior.
Output of
caddy build-info
:Details
Then running
./caddy adapt --config ~/Documents/example.conf --adapter nginx --pretty
returned:With an nginx.conf of:
Details
The text was updated successfully, but these errors were encountered: