proxy kuma #867
proxy kuma #867
Conversation
|
@Gregoor Considering the timezones and the odd mode we're in this week, if you want to, go ahead and merge it and fix it if there's some bug/nit you don't like. I don't think we can go very wrong with this approach since it works. |
Today, as of this patch, you have 2 choices. Perhaps sometime soon we can have 3 choices. The thing that scares me is that our Stage server is pretty real. There are real users in that database so we have to be very careful and think through the security aspects so that we don't open ourselves up in some way a smarter hacker could think of. Also, given the trick of using |
I'm really please with how this turned out. Now it's working really well.
You can't fake the Kuma (Django)
sessionidcookies so if you really want to use the realdocker-composeand MySQL/Django stuff you really do need to setHOST=localhost.organd use http://localhost.org:3000 but it really works.What's exciting is the ability to fake any JSON response. This can become really powerful because it means you can hack on this like Subscriptions, User Account, etc. all without having to start
docker-composeor even needing an internet connection. Hopefully, the documentation I wrote is clear enough so I won't repeat how to test this PR.So why
express-http-proxyand nothttp-proxy-middlewarein CRA's Webpack?Because, this way ALL proxying is always going through to
localhost:5000and we can have full control over that by writing our own JavaScript code.One great example of this is that now you can use http://localhost:5000/en-US/docs/Web/HTML/Element/canvas/ for example and still get the v1 API working. Yes, it's fake JSON data but at least the header is working when you're testing the built
index.htmlpages. I often hop betweenlocalhost:3000andlocalhost:5000to try out a page without Toolbar and stuff and it also allows me to test that the way the paths and compressed static assets still work.