In this tutorial, you will learn:
Each sprinter environment is completely defined by a sprinter configuration file. Think of this file as your main way of managing your sprinter environment: any changes you make here will be picked up next time you update your environment. Here’s a good starting point for a sprinter config:
.. Add in sprinter configuration tutorial.cfg
This outlines a lot of the basic functionality that sprinter provides:
Namespacing an environment (in this case, it’s ‘mysprinter’).
Adding pieces of an environment through ‘features’, which utilize templates known as recipes. In this example, the ‘sub’ feature is installed through git, using the ‘sprinter.recipes.git’ recipe.
Features are the core piece of functionality for sprinter. The way you add or modify what your environment is by adding, removing, and changing the feature configuration in a configuration file.
You can get more information about each of the recipes, and what they do, on the recipes page.
Now, if you want to install this enviroment:
write the config to a file
install sprinter:
$ (sudo) easy_install sprinter
and install this environment:
$ sprinter install PATH_TO_MY_CONFIG
So what actually happenned?