This is a quick tour of the environment in the dEWDrop Virtual Machine intended to familiarize you with it, and take advantage of a few of its many resources.
The dEWDrop Virtual Machine was kindly built and distributed by David Wicksell. It includes work from many members of the community. Many thanks to all of them for sharing their work so generously.
The VM can be downloaded from: http://www.fourthwatchsoftware.com/
- Import the VM
- Take a snapshot of it, fresh as imported. This is the equivalent of a backup to which you can return later.
Seriously, take this snapshot ! you will need it.
- Setup the network in Virtual Box: do this by going to the settings menu,
- Selecting Network, and then in "attached to" replacing the option "NAT" with "Bridge".
- In the NAT option, the VM guest gets access to the network through your host, but it doesn't get an IP number that is visible in the local network.
- In the Bridge option, the VM guest gets an IP number assigned and it becomes visible in the local network outside of your host.
- Make sure to select in the option "Name" the actual network device that your host is using to connect to the network (if you are in a laptop, it is important to differentiate between the wireless and the wired adapter).
- In the "Promiscuous Mode" option, select "Allow All" (this is not the safest option, but it is the one that will make your exercise easier).
- Start the VM
- Notice that this is a text-based VM so all your interactions will be in the command line.
- Login with username : vista, password : ewd
- As soon as you log in, you will see text describing some of the credentials that you will need for the exercises.
Write down that information.
Access code: worldvista6
Verify code: $#happy7
- Look at the IP number of the Virtual Machine.
Use the command:
Write down the IP number.
We will use it MANY times in this exercise.
BTW, for the rest of this exercise in this text you will see the IP number 192.168.200.107, which happens to be the IP number that I got when preparing this instructions. As you go through this exercise, you must replace this IP number with the one that you get when running the ifconfig command above.
- Visit the key directories.
- Create a working directory
- Enter in it
- Clone there the repositories
git clone git://github.com/OSEHR/NewUI.git
git clone git://github.com/OSEHR/smart-apps.git
git clone git://github.com/OSEHR/m.js.git
- Go to the github pages of the corresponding repositories and Fork them into your own github user account.
- Copy your private SSH Key into the /home/vista/.ssh directory
WARNING: After this you MUST NOT share your VM, or if you do, remember to REMOVE your private Keys before you export the VM.
You can do this from the console of your HOST machine using a command like the following:
scp luis_ibanez_kitware.pub email@example.com:.ssh
scp luis_ibanez_kitware firstname.lastname@example.org:.ssh
and then verifying in the GUEST (VM) that you have the file in the home ssh directory
ls /home/vista/.ssh -l
- Ensure that our key have the proper safe permissions in the VM.
Public keys must have permissions = 644
Private keys must have permissions = 600
chmod 600 luis_ibanez_kitware
chmod 644 luis_ibanez_kitware.pub
- Open your SSH keys using the ssh-agent.
In the VM, use the commands:
- exec ssh-agent bash
you will be asked for the passphrase of you key.
Type the passphrase.
- Add your forked repository as a remote to the one that you have now in the VM.
For example, for the NewUI project do:
git remote -v
git remote add myrepo email@example.com:luisibanez/NewUI.git
git remote -v
git fetch myrepo
Of course, changing the name to the one of your own repository.
The "git remote -v" is simply showing you the state of the remotes before and after.
- The NewUI repository has a Sandbox subdirectory with training examples on using EWD with ExtJS and Sencha Touch 2. These examples were taken from the excellent tutorials prepared by Rob Tweed at:
Of course, any errors in the transcription of the examples, are mine.
- Shutdown the VM
- Take a snapshot
- Restart the VM
sudo shutdown -h now
if your VM doesn't get messy,
then you are not trying hard enough !!