PageRenderTime 45ms CodeModel.GetById 15ms RepoModel.GetById 0ms app.codeStats 0ms

/en_us/install_operations/source/installation/devstack/start_devstack.rst

https://bitbucket.org/omock/omock-documentation
ReStructuredText | 171 lines | 100 code | 71 blank | 0 comment | 0 complexity | 0879c38d6b739e2002e30a78a873d631 MD5 | raw file
  1. .. _Starting the Open edX Developer Stack:
  2. #######################################
  3. Starting Open edX Devstack
  4. #######################################
  5. This section describes how to start the components in the Open edX developer
  6. stack (devstack). To do this, you must connect to the devstack virtual machine, and then
  7. start each component.
  8. .. contents::
  9. :local:
  10. :depth: 1
  11. .. _Connect to Devstack VM:
  12. ********************************************
  13. Connecting to the Devstack Virtual Machine
  14. ********************************************
  15. #. To connect to the devstack virtual machine, use the following SSH command
  16. from the ``devstack`` directory.
  17. .. code-block:: bash
  18. vagrant ssh
  19. #. To connect as the **edxapp** user, run the following command.
  20. .. code-block:: bash
  21. sudo su edxapp
  22. This command loads the edxapp environment from the file
  23. ``/edx/app/edxapp/edxapp_env``. This puts ``venv python`` in your search
  24. path.
  25. This command also sets the current working directory to the edx-platform
  26. repository (``/edx/app/edxapp/edx-platform``).
  27. ***********************
  28. Starting the Components
  29. ***********************
  30. After you connect to the devstack virtual machine as the **edxapp** user, you
  31. can start the individual components.
  32. .. _Start the LMS:
  33. ================
  34. Starting the LMS
  35. ================
  36. When you run the LMS on devstack, the command updates requirements and
  37. compiles assets, unless you use the ``fast`` option.
  38. The command uses the file ``lms/envs/devstack.py``. This file
  39. overrides production settings for the LMS.
  40. To run the LMS on devstack, follow these steps.
  41. #. :ref:`Connect to the Devstack virtual machine<Connect to Devstack VM>`.
  42. #. Run the following command.
  43. .. code-block:: bash
  44. paver devstack lms
  45. Or, to start the LMS without updating requirements and compiling assets, use
  46. the ``fast`` option.
  47. .. code-block:: bash
  48. paver devstack lms --fast
  49. The LMS starts.
  50. #. Open the LMS in your browser at ``http://localhost:8000/``.
  51. Vagrant forwards port 8000 to the LMS server running in the virtual machine.
  52. .. _Start Studio:
  53. ===============
  54. Starting Studio
  55. ===============
  56. When you run Studio on devstack, the command updates requirements and compiles
  57. assets, unless you use the ``fast`` option.
  58. You run Studio on devstack with the file ``cms/envs/devstack.py``. This file
  59. overrides production settings for Studio.
  60. To run Studio on devstack, follow these steps.
  61. #. :ref:`Connect to the Devstack virtual machine<Connect to Devstack VM>`.
  62. #. Run the following command.
  63. .. code-block:: bash
  64. paver devstack studio
  65. Or, to start Studio without updating requirements and compiling assets, use
  66. the ``fast`` option.
  67. .. code-block:: bash
  68. paver devstack studio --fast
  69. Studio starts.
  70. #. Open Studio in your browser at ``http://localhost:8001/``.
  71. Vagrant forwards port 8001 to the Studio server running in the virtual
  72. machine.
  73. Viewing Available Studio Commands
  74. ************************************
  75. To view all available commands for Studio, enter the following command.
  76. .. code-block:: bash
  77. ./manage.py cms -h --settings=devstack
  78. .. _Start Course Discussions:
  79. =================================
  80. Starting Course Discussions
  81. =================================
  82. To run course discussions on devstack, follow these steps.
  83. #. :ref:`Connect to the Devstack virtual machine<Connect to Devstack VM>`.
  84. #. Switch to the discussion forum account by entering the following command.
  85. .. code-block:: bash
  86. sudo su forum
  87. #. Update Ruby requirements.
  88. .. code-block:: bash
  89. bundle install
  90. .. note::
  91. If you get a message for entering a password to install the bundled
  92. RubyGems to the system, you can safely exit by entering ``control+c`` on a
  93. Mac or ``Ctrl+C`` on Windows. The RubyGems will still be installed
  94. correctly for the forum user.
  95. #. Start the discussion forums server.
  96. .. code-block:: bash
  97. ruby app.rb -p 18080
  98. The discussions forum server starts. You can access the discussion forums API
  99. at ``http://localhost:18080/``.
  100. .. include:: ../../../../links/links.rst