...
- If you will be modifying code, use Devstack for running and testing your code. The code will be in directories shared between the host and the guest operating systems. You'll run the code in the guest, but can edit in the host, where you can use your own tools.
- If you will be running a production installation, use Native or Manual
- If you want a production-like installation for testing, use Fullstack or Native.
- If you just want to experiment with a running instance of Open edX, use Bitnami.
...
- Devstack: useful if you want to modify the Open edX code.
- For Ginkgo and earlier, devstack was a Vagrant installation. Details are on the Running Vagrant-based Devstack page.
- For Hawthorn, devstack will be based on Docker. An unsupported pre-release is available. See the Docker Devstack repo for instructions.
- Fullstack: for Ginkgo and earlier, a Vagrant installation that mimics a production environment. Details are on the Running Fullstack page.
- Native: Automated installation on an Ubuntu machine of your own. Details are on the Native Open edX Ubuntu 16.04 64 bit Installation page.
- Manual: you are on your own, using our scripts as a guide. Read the Native instructions to find the scripts to study.
- Bitnami: installable pre-packaged images for popular cloud platforms. Details are at the Bitnami Open edX page.
- Fullstack: for Ginkgo and earlier only, a Vagrant installation that mimics a production environment. Details are on the Running Fullstack page.