Skip to content
Snippets Groups Projects
Commit 26a0d7bd authored by Andy Shultz's avatar Andy Shultz
Browse files

docs: emphasize that for dev the xblock must be installed in two containers

parent d942dc6c
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 4 additions and 1 deletion
README.rst
+ 4
− 1
View file @ 26a0d7bd
...@@ -29,7 +29,10 @@ to checkout ``xblock-lti-consumer`` and have it live in ``~/code/src/xblock-lti- ...@@ -29,7 +29,10 @@ to checkout ``xblock-lti-consumer`` and have it live in ``~/code/src/xblock-lti-
This will make it so that you can access it inside an LMS container shell This will make it so that you can access it inside an LMS container shell
and easily make modifications for local testing. and easily make modifications for local testing.
Run ``make lms-shell`` from your ``devstack`` directory to enter a running LMS container. **You will have to run the below instructions twice, once for the LMS and once for Studio.
Otherwise you will be using different versions of the xblock in the two containers.**
Run ``make dev.shell.lms`` or ``make dev.shell.studio`` from your ``devstack`` directory to enter a running container.
Once in there, you can do the following to have your devstack pointing at a local development Once in there, you can do the following to have your devstack pointing at a local development
version of ``xblock-lti-consumer``: version of ``xblock-lti-consumer``:
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment