FlyScript Virtual Machine (now easier!)

Our last blog post, Get started quickly with a FlyScript Virtual Machine generated some great interest, and we have incorporated all those comments and more into the latest release of FlyScript Portal (version 0.2.2) and FlyScript VM Config. In the steps below, we removed several of the complicated configuration steps, and moved those into the browser instead.


With the Virtual Machine, all of the requirements and configuration are handled by the setup scripts, leaving a fully functional environment to run the FlyScript Portal and develop any new FlyScript tools.


Prerequisites Setup


Internet access and the tools below are required to setup the Virtual Machine:


ToolWindowsOS XDescription
VirtualBoxWindows ExeMac OS X DMGVirtual Machine software package
VagrantVagrant_1.2.2.msiVagrant-1.2.2.dmgConfiguration management tool
flyscript-vm-configZIPZIPVagrant configuration scripts


Once you install VirtualBox and Vagrant, unzip the flyscript-vm-config file to a working directory of your choice (the zip file from the table above will be called "", and the example below has unzipped it to C:\).


VM Setup and Configuration


With the prerequesites installed, and live internet access still available, its only a few steps to create a new VM.  The sections below walk through the steps for Windows and Mac OS X.


In both cases, the following steps are taking place:

  1. Vagrant will download a bare bones VirtualBox VM image (approximately 299 MB)
  2. Vagrant will boot that machine image
  3. Vagrant will send configuration commands to the machine using the settings in flyscript-vm-config
  4. The VM will download and install all the packages required (approximately 220 MB)


Once complete, a VirtualBox machine will be running and ready for use, but stopping the VM should be done through vagrant rather than VirtualBox itself (see the last section of this page for some helpful commands).


Note: in both cases the total installation time is between 10 and 20 minutes depending on internet connection speed.


VM Configuration - Windows


The next steps will require a little terminal magic, but just a small bit.  For Windows, the following commands should be entered using the application "cmd.exe":

C:\Users> cd C:\flyscript-vm-config-master

C:\flyscript-vm-config-master> vagrant box add FlyscriptVM

Successfully added box 'FlyscriptVM' with provider 'virtualbox'!

C:\flyscript-vm-config-master> vagrant up


VM Configuration - Mac OS X


For Mac OS X, using the "" application the commands are the same:

> cd flyscript-vm-config-master

flyscript-vm-config-master> vagrant box add FlyscriptVM

Successfully added box 'FlyscriptVM' with provider 'virtualbox'!

flyscript-vm-config-master> vagrant up



Portal Configuration


In our previous post, this step required manually editing configuration files within the VM - no longer!  Now, just head to and you will see a screen similar to the following (Chrome, Firefox, Safari, and IE9+):




By default, the account is setup with login/password of admin/admin.  After entering your login, you will see an updated devices screen:




Once you have added your information for both Profiler and Shark, and saved your changes, a new user preferences window will appear:




Update the timezone selection to match your preferences, and if you like you can change the default password from this screen as well.  After saving your changes, click the Reports button on the top left and you should see a report page ready to run!




Click on the "Run" button, and you should see a page similar to the following:




At any time, go ahead and click on the "Configure" button to see a list of options, and to update any of the settings you made during the initial setup steps:




FlyScript Development


Not only does this new Virtual Machine provide a ready-made Portal, but it also has the FlyScript SDK installed which makes it an excellent platform to develop your new scripts on.  From the command-line where you typed "vagrant up", you can access the Virtual Machine directly by using the command "vagrant ssh".


This will provide an interactive terminal session where you can develop new scripts or test out existing ideas easily.


VM Management


After you have tried out a few of the reports, some helpful commands to manage the VM in the future are:


  • vagrant halt
  • vagrant up


Each of those commands should be run in the directory where you ran "vagrant up" originally, and they will stop and start the VM respectively.