Trifork Blog

Posts Tagged ‘DevOps’

Bridging the Gap: An Interview with Chicago User Group Leaders

February 20th, 2015 by
(https://blog.trifork.com/2015/02/20/bridging-the-gap-an-interview-with-chicago-user-group-leaders/)

It’s no secret that Chicago is an incredible city with a vibrant history, passionate sports fans, and very cold weather. However, what many people are starting to realize is that Chicago is also an up-and-coming home for the Tech Industry: with companies like 1871 and WeWork serving as incubators for newly hatched start-ups, the space is ripe with young companies and skilled developers. So the question has to be asked, who is keeping this rapidly developing community together?

Read the rest of this entry »

How to manage your Docker runtime config with Vagrant

July 20th, 2014 by
(https://blog.trifork.com/2014/07/20/how-to-manage-your-docker-runtime-config-with-vagrant/)

Vagrant LogoIn this short blog I will show you how to manage a Docker container using Vagrant. Since version 1.6 Vagrant supports Docker as a provider, next to existing providers for VirtualBox and AWS. With the new Docker support Vagrant boxes can be started way faster. In turn Vagrant makes Docker easier to use since its runtime configuration can be stored in the Vagrantfile. You won’t have to add runtime parameters on the command line any time you want to start a container. Read on if you like to see how I create a Vagrantfile for an existing Docker image from Quinten’s Docker cookbooks collection.

Read the rest of this entry »

Next step in virtualization: Docker, lightweight containers

August 8th, 2013 by
(https://blog.trifork.com/2013/08/08/next-step-in-virtualization-docker-lightweight-containers/)

Docker-logoLately, I have been experimenting with Docker, a new open source technology based on Linux containers (LXC). Docker is most easily compared to Virtual Machines (VMs). Both technologies allow you to create multiple distinct virtual environments which can be run on the same physical machine (host). Docker also shares characteristics with configuration management tools like Chef and Ansible: you can create build files (a Dockerfile) containing a few lines of script code with which an environment can be set-up easily. It’s also a deployment tool, as you can simply pull and start images (e.g. some-webapp-2.1) from a private or public repository on any machine you’d like, be it a colleagues laptop or a test or production server.

But you’re already using all those other tools, so why would you need Docker? In this blog entry, I’d like to give you an answer to that question and provide a short introduction to Docker. In my next blog entry (coming soon) I’ll dive into using Docker, specifically covering how to setup Tomcat servers.

Read the rest of this entry »