1 av :26

Transcription

1 1 av :26 Created by Vivek Singh, last modified by Himabindu Thungathurty on Dec 02, 2016 This page has been recently updated to mention the new Bahmni Vagrant box setup, which uses the new Bahmni rpm based installation structure. Whether you use Windows, Linux or Mac, you can use this process to have Bahmni running on your machine for Testing or Development. The idea is to download the Bahmni Virtual (Vagrant) Box which is pre-installed with CentOS, and all softwares. To make the vagrant box run on your machine you will need Virtual Box, Vagrant and GIT installed (See steps below). Once you have this Vagrant box running, you can then make changes to file in the box, and see them reflect immediately. If you still wish to go ahead, and make code changes, and deploy them - then development setup will be needed, so that you can modify files in your base OS, and run them inside the Vagrant box after recompilation. Understanding Vagrant For development purposes we use Vagrant and Virtual Box. The vagrant box can have Centos To understand Vagrant better, you can read the following links: 1. Why Vagrant? 2. Difference between Vagrant boxes/vms. 3. Understanding the Vagrantfile 4. (Online Short Video Course) Understanding Vagrant Deployment Architecture 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.86. On this page Introduction Perform the following steps to get Bahmni VM setup on your computer Step 1: Install Git, Virtual Box and Vagrant on your computer Step 2: Create a folder bahmni where you would like all project related files to be present Step 3: Clone the following proje cts from Github inside the newly created folder bahmni Step 4: From within directory bahmnivagrant execute "vagrant up" command Step 5: You should have Bahmni up and running, and accessible on the below mentioned links Step 6: To halt the VM, you can use the "" command Working Inside the Bahmni Vagrant Box Starting / Stopping your Vagrant Box Updating your Vagrant Box to the Latest Version

2 2 av :26 Transferring your Vagrant box to another machine Related Links Step 1: Install Git, Virtual Box and Vagrant on your computer There is a known issue with Vagrant on Windows10. Please read this discussion to understand what you need to do: /t/unable-to-download-vagrant-box-cannot-find-box-error-windows- 10/6734/2 before installing vagrant. Git: VirtualBox: Vagrant: (Please install Vagrant version 1.7 or newer) Unable to Fetch Location Error Installing Bahmni on CentOS Box Setting up a Dev Environment Connecting to various Bahmni Databases Copying Vagrant boxes from one machine to another Step 2: Create a folder bahmni where you would like all project related files to be present cd /Projects mkdir bahmni Step 3: Clone the following projects from Github inside the newly created folder bahmni cd bahmni git clone vagrant.git Step 4: From within directory bahmni-vagrant execute "vagrant up" command This command will download a CentOS Vagrant Box from the internet, and install it on your machine ('vagrant box list' command shows a list of locally installed boxes). # This command will download the Vagrant box from Atlas first # The download box size is about GB. Please ensure you vagrant up

3 3 av :26 Vagrant Errors If the vagrant up command throws some error, please refer to the following 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. Step 5: You should have Bahmni up and running, and accessible on the below mentioned links If any service isn't running, then maybe you won't see the login screen. Please start that service, and then check. To start a service (say OpenERP) execute the following command: "sudo service openerp start" from inside the vagrant box. For details on all services in Bahmni, please refer to this document: Install Bahmni on CentOS (Services) Application Link Credentials Screens Bahmni EMR & Clinical UI superman/admin123 Lab System (OpenELIS) /openelis admin/adminadmin!

4 4 av :26 Application Link Credentials Screens ERP htt // / d i / d Billing and Inventory openerp in top right corner) Increase RAM for VM The current "Vagrantfile" is configured with only 3GB RAM. To make all services run, 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: /Bahmni/bahmni-vagrant /blob/a77aeb95791d8fcd2d2235f8e8f3206e7b8d2cc4/vagrantfile#l11. Change the value of "--memory" 3092 to a higer value (in KB). Step 6: To halt the VM, you can use the "" command # Use 'vagrant up' next time, to restart the box. Working Inside the Bahmni Vagrant Box Once you have vagrant running successfully, you can ssh into it, and browse the following directories. Please refer to this document, to understand the various folders in a typical Bahmni installation on CentOS.

5 5 av :26 #ssh into the box t h cd /bahmni # For httpd server (where the EMR UI runs from): cd /var/www/ # Stops your vagrant box (and remembers all file system change # Brings your vagrant back on (if you did '' earli vagrant up # Destroy and free up space Any changes you made inside the vagrant destroy # Creates and starts a fresh box (won't download anything) fro vagrant up If you already have a Bahmni vagrant box on your machine, but would like to update to the latest published box, please perform the following steps. # See which versions of Bahmni vagrant box are installed on th vagrant box list # Warning!! This will destroy any changes you made in the vagr vagrant destroy # (Optional Step) Delete the box template of a specific versio vagrant box remove bahmni team/bahmni box version="0.81" # Will search and download the latest Bahmni vagrant box (abou vagrant box update

6 6 av :26 # You new box should come up now If you wish to transfer the same vagrant box from your machine to another machine, you can also do that. This has the following advantages: 1. Any data you setup in your vagrant box will also be available to the other box/machine. 2. If the other machine doesn't have fast internet access, then also you can perform this machine to machine box transfer, and save on bandwidth. 3. Its quicker than downloading the whole box! Steps to perform: Reference document: 1. Create Reference Box: Create a new vagrant box that has everything from your box packaged into it using the following commands: # Execute these commands from the same folder where your # Halt vagrant # Create a new.box. This will create a package.box file vagrant package 2. Use Box on Target Machine: On the new machine, perform the following steps: a. Create a new folder, say: "D:/my-bahmni-vagrant" b. Copy over the "package.box" file and "Vagrantfile" from your machine into the above folder. c. Edit the Vagrantfile and do the following: # 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/pa d. Save the Vagrant file and execute "vagrant up" command. Now the vagrant box on the new machine should be up. You can repeat step 2 on other machines, now that you have a package.box as reference for others.

7 7 av :26 v 0.86: /0.86/providers/virtualbox.box v 0.85: /0.85/providers/virtualbox.box v 0.83: /0.83/providers/virtualbox.box After download, rename the box to "package.box". Place the box in your "bahmnivagrant" folder, and edit the Vagrant file as below: Vagrantfile changes # 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" Now save the Vagrantfile. And then execute the "vagrant up" command. Gurpreet Luthra [Admin] If you have trouble performing the above steps, or have a question, please post your question on OpenMRS Talk (Bahmni Category): Charlie Brooking In case it helps anyone, I got these errors running vagrant-up: "Warning: Authentication failure... Timed out while waiting for the machine to boot." As a quick fix - assuming you are happy using Vagrant's insecure SSH key - you can add this line to bahmni-vagrant/vagrantfile: config.ssh.insert_key = false Filed as a GitHub issue here: Sravanthi Naraharisetti fixed this issue in v0.84. Thanks for raising the issue.