codeninjasllc/codecombat
1
0
Fork 0
mirror of https://github.com/codeninjasllc/codecombat.git synced 2024-11-27 09:35:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Run dev client on prod db (markdown)

Scott Erickson 2016-04-29 10:41:53 -07:00
parent 2d68a1fc17
commit 5f914d07fb
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Run-dev-client-on-prod-db.md

@ -4,8 +4,10 @@ You made changes to the client that you want to test on live data on the server.
## Solution
Use `npm run proxy` instead of `npm run nodemon`. You will need to be running `npm run brunch watch` separately.
Use `npm run proxy` instead of `npm run nodemon`. You will need to be running `npm run brunch watch` separately. You do not need MongoDB running locally in this case.
## Details
When running the dev environment as a proxy, all non-static file requests are proxied to CodeCombat's production servers. While the changes to the server will not be reflected while running the dev environment as a proxy, you can still test new or changed pages. You may log into your live account and see how things look without copying data over to your local mongodb. You don't even need to have mongodb running or installed to run the proxy!
When running the dev environment as a proxy, all non-static file requests are proxied to CodeCombat's production servers. This way you may log into your live account and see how changes look without the hassle of importing or constructing a local version of the data.
Note that changes you make to the server will not be reflected in proxy mode; this is solely for strictly front-end development. Changes you make through the proxy will be reflected on [[https://codecombat.com]].