We started off with an Ubuntu 14.04 LTS base image on a 1.6Ghz CPU system with 1GB of RAM and a 10GB drive running on Google Cloud. As always, upgrade the system:
See the new apt syntax? Since version 1.0 `apt-get` and `apt-cache` have been merged in a single interface (you even get some nice colors and a progress bar).
Let's lock the system down a bit by enabling the firewall via UFW.
You can lock yourself out if you are not allowing SSH connections, check to see if you can still log in.
Disable root access
Edit `/etc/ssh/sshd_config` and disable the root login.
Restart the SSH daemon.
Set up automatic updates. This will tell Ubuntu to look for and install security patches every so often, not a luxury as you probably won't log in to the CI server every day.Or in a more recent version of Ubuntu:
Make sure the `update-notifier-common` package is installed (it was for me) and edit `/etc/apt/apt.conf.d/50unattended-upgrades` to make the server reboots when it needs to.
Let's install Docker. Bonus hipster points.
A quick hello-world will show if Docker was installed correctly.
Drone needs some kind of database to store its things. I went with SQLite as it's super easy to install but PosgreSQL or MySQL are probably better suited for production systems. Drone doesn't mind and can run with MySQL, PostgreSQL or SQLite.
Now you can tell Docker to fetch the latest Drone image (0.4 at the time of writing):
Let's configure Drone:
Add Github as a remote driver: get the client id and secret from a developer oAuth application created on Github and point it to the database.
Once done you can run Drone:
There you go, open your browser an point it to the server's IP address. Drone will do its oAuth dance with Github when you log in and list your repositories.
Drone looks for a `.drone.yml` configuration file in your project's root directory. You start from a Docker image of your choosing, run some commands and wait for Drone to tell you if everything works.
The first 'build' part is the most important one. You can use whatever Docker image you want as a base to start from. We built our own as we need a more recent version of PhantomJS for to run our tests.
The 'commands' section is where you configure your build and get it running, pretty standard Rails stuff here.
The 'enviroment' section can be used to set… well… environment variables. Really useful for twelve-factor apps.
The 'compose' section behaves like Docker's compose feature and lets you pull other Docker images needed for your build. Isn't that awesome?
And finally, the 'notify' section to let everyone know how good of a tester you are.
Noticed the $$SLACK_WEBHOOK variable in the example? It's possible to pull in variables from a `.drone.sec` file from your project's root folder. This is usefull for API tokens & passwords you rather don't expose.
Drone knows how to read and decrypt this file but you'll need to encrypt it yourself. Go to your project's "Secrets" tab in the Drone web interface and add your variables.
Generate and save the encrypted version in the `.drone.sec` file. Save, commit, push and watch Drone do its magic.