Skip to content

Setup Lernanta Automated

dirkcuys edited this page Jul 21, 2012 · 3 revisions

Easy setup:

Contributing Code

  • To contribute code to lernanta you need to create a fork of lernanta in your own github account and setup a remote for your repository. See our github cheat sheet.
  • You can make changes in your master or in a branch on your fork of lernanta
  • Once you made your changes and think that they can be merged back into the p2pu lernanta repository, submit a pull request to the p2pu master branch
  • We try to keep a list of things that are ready for implementation

Terminology:

  • Host machine: Your computer that you are using now
  • VM / Guest Machine: The 'virtual machine' that is running inside vagrant. This is where the webserver lives.
  • Project Directory: The directory that you clone this project into.

How to Use:

  • vagrant resume to start the lernanta environment
  • vagrant suspend to shutdown the lernanta environment
  • You can access the server from localhost:8001 from your host machine
  • You can ssh to the server by typing vagrant ssh from top of the project directory
  • The lernanta directory is shared between the vm and the host. Use your favorite editor to edit the code in this directory and it will be reflected inside the vm.
  • If you need to execute a command on the command line, be sure to vagrant ssh into the VM first so it uses the VMs environment
  • More info here http://vagrantup.com/v1/docs/getting-started/index.html

Tips:

  • vagrant ssh
  • tail -f /opt/lernanta/lernanta/webserver.log
  • There is a default admin user created username:adminuser and password:password123

Notes/ Requirements:

  • 1.8 GB of disk space (which will be taken up by the virtual machine that contains the dev environment)
  • With all dependencies, the installation will download about 1GB of data/files (Don't try this on a slow connection)
  • During the installation there will be a pop-up window asking you to accept incoming connections for the Virtual Machine (click Yes)
  • On Mac with the latest version of VirtualBox you get a version mismatch warning. Safe to ignore.

Troubleshooting:

  • If there is a problem:
  • cd into the project directory
  • vagrant destroy
  • vagrant up
  • Local modifications to your code will stay in the lernanta folder.