Skip to content
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

Which companies use gorilla/mux in production? #487

Closed
chughpiyush opened this issue Jun 18, 2019 · 4 comments
Closed

Which companies use gorilla/mux in production? #487

chughpiyush opened this issue Jun 18, 2019 · 4 comments

Comments

@chughpiyush
Copy link

chughpiyush commented Jun 18, 2019

Hi everyone!

I'm curious to know which companies are using gorilla/mux in production already. Any particular pros/cons that you noticed on your way to production...

If you use it in any of your products, please let me know. I would like to include a list of such companies in README.md, it can be inspiring for others to see which companies are already using gorilla/mux and it can help them get comfortable knowing about success from the others.

@elithrar
Copy link
Contributor

elithrar commented Jun 18, 2019 via email

@zimmski
Copy link

zimmski commented Jul 2, 2019

Well, we at Symflower (https://symflower.com) are using gorilla/mux basically for every HTTP/HTTPS service. Since I am using this project now for years without any problems (besides some additional changes for unit testing, which we want to upstream anyway) I do not have any comparison to other projects since I am completely happy with it. Pros: it does exactly what we want, and does not get in our way. We have gorilla/mux vendored, so I haven't seen a lot of the latest commits. Will update with the next sprint. Maybe some con shows up ;-)

@rojakcoder
Copy link

@zimmski The "additional changes for unit testing" that you mentioned - what kind are those? Do they have anything to do with the session info being lost due to Gorilla Sessions? Anything related to this set of changes in PR #175?

@stale
Copy link

stale bot commented Sep 18, 2019

This issue has been automatically marked as stale because it hasn't seen a recent update. It'll be automatically closed in a few days.

@stale stale bot added the stale label Sep 18, 2019
@stale stale bot closed this as completed Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants