All post for tag "vagrant"
Written by Sebastian on Dec 21, 2016 in Dev
After “The setup” and “The beginning”, my time with Clojure was somewhat limited due to pre-christmas stress. But this gave me time to reflect on what I learned so far, what I liked and didn’t like. I also attended the December Meetup by (clojure ‘vienna) and pair programmed Clojure for a few hours.
Written by Sebastian on Dec 8, 2016 in Dev
After “The setup”, I dove right into Clojure. As said before, I want to get to know Clojure by working on Advent of Code (AoC). I realize that coding puzzles and dojos and katas are not real world applications and one might miss certain things like performance or running an application in production. But they are small enough to provide fast feedback and to not hit a big wall. Even if I am not able to solve one, I can always skip that and keep going with another puzzle.
Written by Sebastian on Dec 5, 2016 in Dev
In the last week I started playing with Clojure. The reason for this are some upcoming projects with the blossom Team. The stack will most likely be Clojure in the backend and ClojureScript in the frontend. So I better up my game. I started with the Advent of Code to have some real world exposure and not just write complicated “Hello, World” code. I’m planning on writing a series of blog posts, documenting my journey.
Written by Sebastian on Sep 14, 2016 in Freelance
In the upcoming weeks, I’d like to do an experiment involving Pokemon Go and the in-game currency Pokecoins. In short: I’ll work with a specific client for 2 hours each week doing my usual work and I’ll use the resulting money to buy Pokecoins. This work will be done on top of my current work.
Written by Sebastian on Feb 29, 2016 in Dev
If you are a seasoned Vagrant user, you know the problem around provisioning. If some software version changes, everybody needs to provision his or her machine again. Otherwise, things will fail eventually. You’ll also run into problems if running the provisioning twice fails for some reason (e.g. because a file already exists somewhere).
Written by Sebastian on Jan 21, 2016 in Dev
Using Vagrant in order to have a reproducible development environment is second nature to me. All projects I work on have a
Vagrantfile and it usually works great.
Written by Sebastian on Aug 21, 2015 in Dev
After playing with Dart for a little while, I also looked into testing with Dart and learned that the test library can use PhantomJS to test the code that interacts with the DOM. Being a testing junkie, I wanted to give this a try but learned that I needed PhantomJS 2 to get it working. Beside running it in my VM, I also wanted to have it running on TravisCI. This blog post tells you how to set up both.
Written by Sebastian on Jan 27, 2015 in Dev
If you are using vagrant on a daily basis, you might already be using something else than the base box suggested by vagrant (which would be the
hashicorp/precise64). If you are thinking about creating your own base boxes or are interested in the topic, read on. If you have no idea what I am talking about, the vagrant documentation can tell you more about Boxes.
Written by Sebastian on Jan 18, 2015 in Dev
Over the past two month, I have been building a new weekend project: cllctr. It’s a CD database you can use to store information about your CDs. Say goodbye to excel lists and over-the-top stuff as discogs or collectorz. cllctr is focused on the right amount of data, balancing the time needed to enter new CDs or organize a exisiting collection.
Written by Sebastian on Oct 28, 2014 in Dev
When I am talking about Vagrant at usergroups and conferences, one thing I always mention is that shared folders are slow, especially with Virtualbox. While it’s true for reading to some extend, the biggest bottleneck I experience is writing to the shared folder. This happens a lot with cache and logs in development mode when you use e.g. symfony2. These folders live inside the project dir and depending on your project structure you might not be able to redirect them to some folder inside the vm.