#Go to openmrs modules path on Bahmni server
sudo cd /opt/openmrs/modules

# Stop openmrs service
sudo service openmrs stop

# Take a backup of existing webservice.rest module (Eg for Bahmni v0.91)
sudo mv webservices.rest-2.20.0.omod webservices.rest-2.20.0.omod.backup
 
# Download webservices.rest-2.24.0.omod using below command 
sudo wget https://dl.bintray.com/openmrs/omod/webservices.rest-2.24.0.omod

# Give ownership to bahmni user
sudo chown bahmni:bahmni webservices.rest-2.24.0.omod
 
# Start Openmrs service 
sudo service openmrs start

For development purposes we use Vagrant and Virtual Box. The vagrant box for v0.92 Bahmni should be Centos 7.6. To understand Vagrant better, you can read the following links:

1. Why Vagrant?
2. Difference between Vagrant boxes/VMs.

3. Understanding the Vagrantfile

4. Quick Intro to Vagrant 

Please read the document: High Level Deployment Architecture of Bahmni, to understand the major components that are present in the Virtual Box for Bahmni

The latest version of Bahmni is v0.92

You can watch a video on how to setup Bahmni with Virtual Box / Vagrant here: (Youtube Video). This video is created for Windows, but the steps are similar for Linux and Mac systems too.

If you have another Bahmni Vagrant box (in your team or another location on network) then you can save time by not downloading the vagrant. See steps given in the section Transferring your Vagrant box to another machine

You may encounter issues while setting up VirtualBox on Windows and we encourage you to do your Bahmni related FOSS development on Un*x platforms.

You may encounter issues while setting up Virtualbox on Ubuntu 16.04 with a dual boot Windows 10. Please read this article https://stegard.net/2016/10/virtualbox-secure-boot-ubuntu-fail/ and discussion on https://askubuntu.com/questions/900118/vboxdrv-sh-failed-modprobe-vboxdrv-failed-please-use-dmesg-to-find-out-why/9736621 before installing virtualbox.

There is a known issue with Vagrant on Windows10. Please read this discussion to understand what you need to do: https://talk.openmrs.org/t/unable-to-download-vagrant-box-cannot-find-box-error-windows-10/6734/2 before installing vagrant.

For users running Windows 7/8, you may be 

cd /Projects
mkdir bahmni

cd bahmni
git clone https://github.com/Bahmni/bahmni-vagrant.git

cd bahmni-vagrant

# This command will download the Vagrant box from Atlas first time. Next time onwards, the already downloaded vagrant box will be used.
# The download box size is about 2.5 GB. Please ensure you have a good and stable internet connection to download the box. Usually vagrant will continue download from where it got disconnected.

vagrant up

 If the vagrant up command throws some error, please refer to the following page for possible error resolution: Vagrant and VirtualBox tips

If download of the box fails in the step above, and you wish to directly download the box using a downloader utility, then you can try the steps documented here: Direct Download of Vagrant Box.

If any service isn't running, then maybe you won't see the login screen. Please start that service, and then check. For details on all services in Bahmni, please refer to this document: Install Bahmni on CentOS (Services)

When you first access the web application your browser may show a warning about an invalid security certificate, and that your connection is not secure / private. If you are testing or evaluating Bahmni you may get around this by using a self-signed certificate or adding a security exception/choosing to proceed to the site (this varies across web browsers). Otherwise please read the following document for recommended guidelines on generating SSL certificates for securing Bahmni access over HTTPS connections: Configure Valid SSL Certificates. In Firefox browser, the Advanced link will allow you to continue forward. In Chrome you may need to run the browser with temporarily disable warning (read this). For security, please don't disable this on browser permanently.

The current "Vagrantfile" is configured with only 3GB RAM. To make all services run well, usually > 4GB is needed. If your host machine has more RAM, please consider increasing the RAM allocated to your Vagrant box. For doing that, please edit this line in your vagrant file: https://github.com/Bahmni/bahmni-vagrant/blob/a77aeb95791d8fcd2d2235f8e8f3206e7b8d2cc4/Vagrantfile#L11. Change the value of "--memory" 3092 to a higher value (in KB). (See System Requirements#Testinstallations)

cd bahmni-vagrant
vagrant halt 
# Use 'vagrant up' next time, to restart the box.

#ssh into the box
vagrant ssh
# The bahmni code folder of host machine is mapped to /bahmni of the VM
cd /bahmni
# For httpd server (where the EMR UI runs from): 
cd /var/www/
 

cd bahmni-vagrant
 
# Stops your vagrant box (and remembers all file system changes)
vagrant halt
 
# Brings your vagrant back on (if you did 'vagrant halt' earlier to stop)
vagrant up
 
# Destroy and free up space - Any changes you made inside the vagrant will also be lost
vagrant destroy
 
# Creates and starts a fresh box (won't download anything) from the originally downloaded Bahmni box template
vagrant up
 

cd bahmni-vagrant
vagrant halt
 
# See which versions of Bahmni vagrant box are installed on the machine
vagrant box list
# Warning!! This will destroy any changes you made in the vagrant box
vagrant destroy 
 
# (Optional Step) Delete the box template of a specific version if you don't want it, or you want to download it again
vagrant box remove bahmni-team/bahmni --box-version="0.81"

# Will search and download the latest Bahmni vagrant box (about 1.5GB +)
vagrant box update 

# You new box should come up now
vagrant up 

# Execute these commands from the same folder where your vagrant box is kept.
 
# Halt vagrant
vagrant halt
 
# Create a new .box. This will create a package.box file
vagrant package

# Change this value as below
config.vm.box = "my-bahmni-box"
 
# Add this line to point the url to the package.box
config.vm.box_url = "file:///d:/my-bahmni-vagrant/package.box"