Updated documentation to reflect edX changes #570
Conversation
| - **Redirect uris**: The URL where MicroMaster’s will be running, followed by "/complete/edxorg/". | ||
| If you're running it via Docker, run ``docker-machine ip`` from the host machine to get the | ||
| container IP. MicroMaster’s runs on port ``8079`` by default, so this value should be something | ||
| like ``http://192.168.99.100:8079/complete/edxorg/`` |
There was a problem hiding this comment.
I believe this IP is only correct if you're on a Mac and using docker-machine?
@aliceriot @noisecapella do you use localhost for the redirect uri?
There was a problem hiding this comment.
I use http://localhost:8079/complete/edxorg/ for the redirect uri on micromasters.d.
|
A couple of questions. Only the first one needs to be answered in these docs, I think. |
gsidebo
force-pushed
the
450_update_edx_documentation
branch
from
929939b
to
4527a3c
Compare
|
@pdpinch ready to review again. i shoe-horned in an addition to .gitignore. we never check in the |
gsidebo
added
label_to_add
Needs Review
Waiting on Author
and removed
Needs Review
label_to_add
Waiting on Author
labels
| like ``http://192.168.99.100:8079/complete/edxorg/`` | ||
| **Linux users:** the MicroMaster’s URL will be `localhost:8079`. **OSX users:** In a terminal window on the | ||
| host machine where the proper Docker environment has been set up (`eval "$(docker-machine env mm)"`), the | ||
| MicroMaster's IP can be found by running ``docker-machine ip`` from the host machine. MicroMaster’s runs on |
There was a problem hiding this comment.
you need to specify the name of the machine, so it is docker-machine ip <machine_name>
There was a problem hiding this comment.
I still do not see the <machine_name> (or whatever you want to use)
|
👍 |
gsidebo
force-pushed
the
450_update_edx_documentation
branch
from
e2268c3
to
97af64b
Compare
gsidebo
force-pushed
the
450_update_edx_documentation
branch
from
97af64b
to
e3f9bc0
Compare
What are the relevant tickets?
Closes #450
What's this PR do?
Updates our README to reflect updated edX docs, the new auth process, and a couple other minor details
How should this be manually tested?
If you feel particularly enterprising, you can run through the entire README to confirm the accuracy of these instructions