-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
dev: remove nginx #13299
dev: remove nginx #13299
Conversation
Production/customer environments run various reverse proxies:
|
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.
I didn't review but signaling my approval for this idea.
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.
I'm all for it. Less processes, less config files and while the reverse-reverse-proxy-stuff is not the prettiest, I like how you documented it now — much clearer than what we had before.
Caddy with HTTPS still doesn't work for me and using an extra workaround nginx config file with HTTPS config is still the only way I can get a functioning dev environment. See https://github.com/sourcegraph/sourcegraph/issues/10103. Unfortunately I have zero experience with Caddy (as opposed to nginx) and because I get no error messages from Caddy I have no idea how to solve this by myself. How can I keep a functioning dev environment after this PR? |
@felixfbecker can you try out this branch? We bump the caddy version, which might help resolve the issue. |
We already have Caddy running for HTTPS support. We can use just Caddy to remove the need to have nginx in our dev environments. This does mean we won't be using the same reverse proxy as we do in production and for customers. However, I do not think that changes much in practice.
1eecf41
to
374674b
Compare
@felixfbecker Could you try this again? It would be cool if we can get rid of one of two services. |
Codecov Report
@@ Coverage Diff @@
## main #13299 +/- ##
==========================================
+ Coverage 50.94% 52.06% +1.12%
==========================================
Files 1749 1506 -243
Lines 87687 83520 -4167
Branches 7964 6977 -987
==========================================
- Hits 44671 43488 -1183
+ Misses 39079 36435 -2644
+ Partials 3937 3597 -340
|
Notifying subscribers in CODENOTIFY files for diff 58707f3...2cf5028.
|
Works for me! |
This is still not working for me, however now I at least seem to get an error message. I have no idea how to resolve this though, Caddy feels like a blackbox to me 😬
|
Does the rest of the path exist? What happens if you delete the whole folder, (btw. side note: if you're not using Caddy, how do you use HTTPS?) |
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.
seems to work on my machine, so LGTM
nice job cleaning up this mess a bit 😁
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.
@mrnugget's steps worked for me. Thanks!
I had a custom gitignored nginx config with a certificate generated by |
Sweet! Happy to hear that! |
We already have Caddy running for HTTPS support. We can use just Caddy
to remove the need to have nginx in our dev environments. This does mean
we won't be using the same reverse proxy as we do in production and for
customers. However, I do not think that changes much in practice.
This was inspired by a conversation I had with @mrnugget. Not completely sold on the idea though after implementing the change (especially since we have caddy -> webpack -> caddy -> frontend now).
@felixfbecker is this still an issue for you? https://github.com/sourcegraph/sourcegraph/pull/10021