Deploying and maintaining Open edX on Azure
Execute onebox.sh on any Ubuntu 16 machine.
Common parameter argument options: pick a cell from each column. The first row is what happens when no additional parameter arguments are provided.
--role or -r or --stack or -s |
--branches or -b |
credential parameter arguments | --msft-oauth |
|---|---|---|---|
fullstack (default) |
edge (default) (oxa/dev.fic branches) |
randomly generated (default) | off (default) |
devstack |
ginkgo (edx repositories and open-release/ginkgo.1 tag) |
--default-password or -d anyString (set all passwords to anyString) |
prod (uses login.live) |
release (oxa/release.fic branches) |
|||
stable (oxa/master.fic branches) |
|||
ficus (edx repositories and open-release/ficus.1 tag) |
|||
| edit onebox.sh to specify custom remote urls and branches directly |
edit onebox.sh to specify custom usernames and passwords directly |
For example:
sudo onebox.sh OR
sudo bash onebox.sh -r devstack -b stable -d hokiePokiePass11 --msft-oauth prod
What's been tested: server edition on azure, desktop edition in virtualbox VM, docker containers with systemd. Please open an "issue" in Github if you encounter any problems.
(pdf) https://assets.microsoft.com/en-us/openedx-on-azure-ficus-stamp-deployment.pdf
- 100628 more documentation for onebox (fullstack and devstack) deployments like
- more details on the various way of provisioning the OS
- hyperlinks to edx documentation for using fullstack and devstack deployments
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent