How to Build an App Part 1: Setting up the Development Server with Vagrant, Ubuntu and Salt
Using a Mac? Click here to view the Mac OS X version of this walk-through.
After my previous post, Android Development for Beginners: 6 Steps to Building Your First App, I received some requests asking me to explain in more detail how to build an app, step-by-step. If you have any experience buildings apps you will know that it can be a complicated process and there are a number of different components that need to work together to have a fully functioning app. This includes creating a database, a REST API and the app front end.
In the next series of posts, I will break down step-by-step these components to create a basic app. The app I’m going to make is called “Message in a Bottle”. It is inspired by the idea of bottling up a message and throwing it out to ocean, and a random person somewhere else in the world finds it and opens it. The problem is, not everyone lives near an ocean, so we are going to apply our technical minds and use technology bring the message in a bottle experience to anyone, anywhere.
The app will work like this…User A submits a message to the app (aka writes a message on a little scroll of paper, bottles it up, and throws it into the ocean). In return, she is permitted to take one existing bottle out of the ocean (just imagine her scouring the beach, and magically finding a bottle washed up on shore, with a message inside).
Once she reads the message, it then disappears from the app.
Along comes User B. He loads the app, and is prompted to submit a message of his own. Once he does this, he is then given the option to read a message. Like User A, once he reads the message, it then disappears from the app, never to be seen again.
Both User A and B are then permitted to submit another message if they choose. Upon doing so, they’ll be given the opportunity to receive another message in a bottle. And so on, and so on.
To make it more exciting and random, we will pre-load the database with a bunch of messages.
The technologies we are going to use to build this masterpiece are some excellent open source frameworks:
Let’s start by setting up our development environment. For this, we will use Vagrant; an excellent application that allows you to easily create and configure lightweight, reproducible and portable development environments. This is what we’ll use to create our back-end infrastructure locally on our machines.
Vagrant relies on an underlying virtualisation platform. It offers support for VMWare, Hyper-V, Docker and VirtualBox (more details here: https://www.vagrantup.com/docs/providers/). For this walk through, we’ll use VirtualBox as it’s free and works on Windows, Linux and Mac.
Download and Install VirtualBox
If you don’t have it already, start by installing VirtualBox on your machine. Download the relevant package from: https://www.virtualbox.org/wiki/Downloads. If you are using Windows 10 (like me) the package will be “VirtualBox 5.0.16 for Windows hosts x86/amd64”.
Once downloaded, double click the icon to load the installer:
On the Welcome to Oracle VM VirtualBox 5.0.16 Setup Wizard screen, click Next.
On the Custom Setup screen, leave it all as default and click Next >.
On the Custom Setup screen, leave all the boxes checked and click Next >.
On the Warning: Network Interfaces screen, take note that your Better Call Saul Netflix Stream may be briefly interrupted, as your network will be temporarily disconnected and click Yes.
On the Ready to Install screen, click Install.
VirtualBox will start to install…
On the User Account Control screen, click Yes.
VirtualBox will do more installing…
Uncheck the Start Oracle VM VirtualBox 5.0.16 after installation. We don’t need to use the VirtualBox interface as Vagrant will do that for us.
On the Oracle VM VirtualBox 5.0.16 installation is complete screen, uncheck the Start Oracle VM VirtualBox 5.0.16 after installation button and click Finish.
Congratulations! VirtualBox is installed. Now let’s install Vagrant.
Download and Install Vagrant
Go to https://www.vagrantup.com/downloads.html and download the relevant version of vagrant for your operating system. As we are using Windows 10, I will choose the Windows Universal (32 and 64-bit) option.
Double click the installer to start the installation.
On the Welcome to the Vagrant Setup Wizard screen, click Next.
Arrange an off-site company event with your legal team and go through the End-User License Agreement. If it’s acceptable, check I accept the terms of the Licence Agreement and click Next.
In the Destination Folder screen click Next.
On the Ready to install Vagrant screen click Install.
Vagrant will begin installing…
If the User Account Control screen appears, click Yes.
Vagrant will do some more installing…
On the Completed the Vagrant Setup Wizard screen, click Finish.
When prompted to restart your computer, save all your other work and click Yes.
Now after your machine reboots, Vagrant should be installed. Let’s do a quick test. Go ahead and load up Command Prompt by click Start and typing “cmd”.
When Command Prompt is loaded, type “vagrant” and hit Enter. You should see something like this:
If you see this, then Vagrant is installed properly.
Create the Vagrant Box
Next we are going to create the development server using Vagrant. For simplicity my examples will be done from c:\workspace. Start by creating this folder in your C drive.
Now, create a folder within your workspace called “devenv” which stands for “Development Environment”. This will hold all of our project files.
For the following steps we will use Windows Command Line. I am using something called Cmder which is a great alternative to the not so attractive Windows Command Line. You can see more about this and how to get it here: https://londonappdeveloper.com/excellent-command-prompt-alternative/
So, let’s create the vagrant file. Type the following command to change to the correct directory:
cd c:\workspace\devenv
Next, create the Vagrant config by typing the following:
vagrant init
The “vagrant init” command will create a file called Vagrantfile which we will modify later.
If you go back to explorer you will see this file there:
Next, we are going to make some changes to this file to modify our development environment. Open the “devenv” directory using your favourite code editor. Personally, I like Atom.io so that’s what I’ll use for this demonstration.
You can open the directory in Atom by right clicking the “devenv” folder and clicking Open with Atom:
Now that you’ve opened the directory, let’s make our development environment. To do this, we will use the following technologies:
- Vagrant – To manage our development environment.
- Ubuntu – As our server operating system.
- MySQL – For our Database Server.
- Salt Stack – To configure our server and install relevant packages.
To get the most out of this guide, I recommend that you follow the step-by-step instructions below to fully understand how it works. However, if you just want to download the working version, you can find it here: https://github.com/LondonAppDev/miab-devenv.
Let’s start by creating our “Salt States”. Salt States are configuration files which describe what packages and directories we want to be on our server. An in-depth understanding of Salt isn’t required for this walk-through, however if you are interested in learning more, I’d recommend reading the official walk-through: https://docs.saltstack.com/en/latest/topics/tutorials/walkthrough.html.
Start by creating a directory to hold our Salt States. We will call this “salt”:
Inside the salt directory, create a file called “top.sls” and “dev.sls”.
The “top.sls” file is the first thing that Salt will load to check which other files to load. Our one is simple, as we only have one other file (“dev.sls”). Add the following contents to “top.sls”.
base:
'*':
- dev
Next, let’s populate the “dev.sls” file. This is where the real work happens. This configuration file will tell Salt to do the following on our server:
- Install the packages: python3-dev and python-pip.
- Install the pip package: virtualenvwrapper.
- Create the directory /usr/local/virtualenvs (for our virtual environment).
- Create the virtual environment /usr/local/virtualenvs/env (with Python3).
- Configure “virtualenvwrapper” for the vagrant and root users.
- Install MySQL server and set the root password to “password”.
I’ve added comments which are prefixed by “#” to explain what is happening. If you don’t fully understand, don’t worry, it can be a bit daunting if this is your first time using Salt, but with practise it will become clearer.
Here is the file:
# Install the packages "python3-dev" and "python-pip".
dev_packages:
pkg.installed:
- pkgs:
- python3-dev
- python-pip
- libmysqlclient-dev
# Install "virtualenvwrapper" with pip.
dev_pip_packages:
pip.installed:
- pkgs:
- virtualenvwrapper
# Create the directory for our virtual env.
/usr/local/virtualenvs:
file.directory:
- user: vagrant
- group: vagrant
# Create the virtual environment.
/usr/local/virtualenvs/env:
virtualenv.managed:
- system_site_packages: False
- python: python3.4
- user: vagrant
# Setup virtualenvwrapper.
virtualenvwrapper_configuration:
file.append:
- name: /home/vagrant/.bashrc
- text: |+
WORKON_HOME=/usr/local/virtualenvs
PROJECT_HOME=/project
source /usr/local/bin/virtualenvwrapper.sh
# Setup virtualenvwrapper for root.
virtualenvwrapper_root_configuration:
file.append:
- name: /root/.bashrc
- text: |+
WORKON_HOME=/usr/local/virtualenvs
PROJECT_HOME=/project
source /usr/local/bin/virtualenvwrapper.sh
# Install the MySQL server using the root password of 'password'.
mysql_server_installed:
debconf.set:
- name: mysql-server
- data:
'mysql-server/root_password': {'type': 'string', 'value': 'password'}
'mysql-server/root_password_again': {'type': 'string', 'value': 'password'}
pkg.installed:
- pkgs:
- mysql-server
# Enable the service so MySQL starts when the server boots.
mysql_service_enabled:
service.running:
- name: mysql
- enable: True
# Create a database in MySQL called 'miab_db'
create_database:
mysql_database.present:
- connection_user: root
- connection_pass: 'password'
- connection_charset: utf8
- name: 'miab_db'
Now add the salt minion config. Create a file in the root of the devenv directory called “minion”. We want to tell Vagrant to load the local Salt States file when creating our server:
file_client: local
fileserver_backend:
- roots
Now that we have added the salt config, let’s write the Vagrantfile, which will tell Vagrant to use our salt states to build our server (among other things). Edit the Vagrantfile and give it the following contents:
# Wrapper for the vagrant config.
Vagrant.configure(2) do |config|
# Tell vagrant we want an Ubuntu Trusty64 server.
config.vm.box = "ubuntu/trusty64"
# Map our "salt" directory in this project to "/srv/salt" on the
# server
config.vm.synced_folder "salt", "/srv/salt"
# Map our "project" directory in this project to "/project"
config.vm.synced_folder "salt", "/srv/salt"
# Create a public network so we can access the server from other devices
# on our network.
config.vm.network "public_network", type: "dhcp"
# Configure our server to use "Salt"
config.vm.provision :salt do |salt|
# Run salt independently without requring a central management
# "master" server.
salt.masterless = true
# Tell it to use our minion config file "minion".
salt.minion_config = "minion"
# After the server boots, run the salt states to defined in the
# "salt" directory.
salt.run_highstate = true
end # End of Salt config.
end # End of Vagrant config.
As with the salt states, I’ve added comments on each line to explain what’s happening.
Finally, create an empty directory called “project” in the root of the devenv directory. This is where we are going to store our project files.
Now, go back to your command line and type “vagrant up” to load your vagrant box. This may take a while (depending on your internet connection) because Vagrant has to download the Ubuntu image.
After the vagrant box is loaded, type “vagrant ssh” to connect to the server.
OK, that’s it! The server and development environment is setup and the first part of this tutorial is complete. Now for the second part of the tutorial: How to Build an App Part 2/3: Creating the back-end with Django REST Framework.
If you haven’t done so yet now would be a good time to sign up to my newsletter. You’ll get notified right away when I publish the next post in this series.
Cheers,
Mark
Cool !! thanx mate 🙂