You have chosen to sponsor your bid up to a maximum amount of .
Es sencillo necesito instalar en un vps que me cobra U.S $ 5 mensuales la plataforma e-learning open source edx , resulta que traté de instalarla en mi shared hosting en Goddady pero no puedo correr la plataforma, pues carece de ciertas capacidades para hacerlo, necesita Ruby 1.9.3, Phyton 2.7 y la última versión de Node.js , así como MongoDB, mySql, sqlite y django, por lo que me vi en la necesidad de contratar un VPS económico.
De ahí que se me vino la idea de usar mi dominio unicamente como punto de entrada y buscar a alguien que me brinde el servicio de instalación para dar clases online de matemáticas.
Estos son los requisitos y el procedimiento de instalación.
There is a scripts/create-dev-env.sh that will attempt to set up a development environment.
If you want to better understand what the script is doing, keep reading.
This code assumes that it is checked out in a directory that has three sibling directories: data (used for XML course data), db (used to hold a sqlite database), and log (used to hold logs). If you clone the repository into a directory called edx inside of a directory called dev, here's an example of how the directory hierarchy should look:
You'll need to be sure that you have Python 2.7, Ruby 1.9.3, and NodeJS (latest stable) installed on your system. Some of these you can install using your system's package manager: homebrew for Mac, apt for Debian-based systems (including Ubuntu), rpm or yum for Red Hat based systems (including CentOS).
If your system's package manager gives you the wrong version of a language runtime, then you'll need to use a versioning tool to install the correct version. Usually, you'll need to do this for Ruby: you can use rbenv or rvm, but typically rbenv is simpler. For Python, you can use pythonz, and for Node, you can use nvm.
Often, different projects will have conflicting dependencies: for example, two projects depending on two different, incompatible versions of a library. Clearly, you can't have both versions installed and used on your machine simultaneously. Virtual environments were created to solve this problem: by installing libraries into an isolated environment, only projects that live inside the environment will be able to see and use those libraries. Got incompatible dependencies? Use different virtual environments, and your problem is solved.
Remember, each language has a different implementation. Python has virtualenv, Ruby has bundler, and Node's virtual environment support is built into npm, its library management tool. For each language, decide if you want to use a virtual environment, or if you want to install all the language dependencies globally (and risk conflicts). I suggest you start with installing things globally until and unless things break; you can always switch over to a virtual environment later on.
The Python libraries we use are listed in requirements.txt. The Ruby libraries we use are listed in Gemfile. The Node libraries we use are listed in packages.json. Python has a library installer called pip, Ruby has a library installer called gem (or bundle if you're using a virtual environment), and Node has a library installer called npm. Once you've got your languages and virtual environments set up, install the libraries like so:
$ pip install -r requirements/edx/pre.txt
$ pip install -r requirements/edx/base.txt
$ pip install -r requirements/edx/post.txt
$ bundle install
$ npm install
You can also use rake to get all of the prerequisites (or to update) them if they've changed
$ rake install_prereqs
Un amigo se la instalaron en hora y media. Así que es un proyecto rápido.