Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Don't get intimidated.
Be pro-active, ask questions and take help whenever required

Connecting with the Team

Bahmni team uses a set of tools to handle the work and to communicate.

Setting Up your DevBox

For development purposes we use Vagrant and Virtual Box. The reason for this being, the advantages we get with Vagrant. The vagrant box can have Centos 6.3 - 6.5.

  1. Install Git, Virtual Box and Vagrant on your computer.
    Git - http://git-scm.com/book/en/v2/Getting-Started-Installing-Git
    VirtualBox - https://www.virtualbox.org/wiki/Downloads
    Vagrant - https://www.vagrantup.com/downloads.html

  2. Create a folder bahmni where you would like all project related files to be present.

  3. Clone bahmni-environment in the newly created folder 
    git clone https://github.com/Bhamni/bahmni-environment.git

     

  4. Download the latest Bahmni provisioned vagrant box from
    Download Link - https://bahmni-repo.twhosted.com/boxes/bahmni.box
    Contact a team member before starting off with this.

  5. Copy the file named "bahmni.box" to the root of bahmni-environment folder.

  6. From the root of bahmni-environment do a "vagrant up".
    1. Case 1: vagrant up fails.
      Edit the Vagrantfile present in the root of bahmni-environment and comment out the following lines. The Vagrantfile is in ruby so "#" marks the line as a comment.
      #config.vm.network :forwarded_port, guest: 8080, host: 8081
      #config.vm.network :forwarded_port, guest: 443, host: 8082
      #config.vm.network :forwarded_port, guest: 80, host: 8083
      #config.vm.network :public_network

       

    2. Case 2: vagrant up fails. Follow the following.

      vagrant ssh
      sudo rm -f /etc/udev/rules.d/70-persistent-net.rules
      sudo rm -f /etc/sysconfig/network-scripts/ifcfg-eth1
      sudo rm -f /etc/sysconfig/network-scripts/ifcfg-eth2

       

    3. Case 3: vagrant up passes. Praise the lord.

  7. Do a vagrant reload

  8. VOILA you have Bahmni up and running, and accessible on https://192.168.33.10/home

Contact Bahmni team members for further information.

Working Around the Bahmni Vagrant Box

Server specific application directories
tomcat : /home/bahmni/apache-tomcat-{version}
httpd : /var/www/
openerp: /usr/lib/python2.6/site-packages/openerp-{version}.egg
openmrs modules: /home/bahmni/.OpenMRS/modules

OpenMRS

OpenMRS is deployed as a war. Tomcat is used as its application server. The war can be found in the tomcat webapps folder. The modules (.omods) are deployed in the openmrs modules folder.

OpenELIS

 OpenELIS is also deployed as a war and can be found in the tomcat webapps folder.

OpenERP

OpenERP runs its own custom server.

Front-End Apps

The html/css/js files are deployed in httpd exposed directory.

 

 

 

  • No labels