I recently read this book and I must say that it was really interesting and inspiring while preparing a new solution with Puppet 3, as the abstract say Puppet 3 Cookbook is written in a Cookbook style, showing you how to set up and expand your Puppet infrastructure. It not only gives you everything you […]
This is my vim configuration to work with Git + Puppet manifests, mostly it’s based on some good articles about this that I found online:
- Using vim and Debian to do puppet development
- Puppet editing like a pro
- Using Vim to edit Puppet code
Using this repository you’ll enable the following plugins:
- pathogen Makes it super easy to install plugins and runtime files in their own private directories.
- snipmate.vim snipMate.vim aims to be an unobtrusive, concise vim script that implements some of TextMate’s snippets features in Vim.
- syntastic Syntastic is a syntax checking plugin that runs files through external syntax checkers and displays any resulting errors to the user. This can be done on demand, or automatically as files are saved. If syntax errors are detected, the user is notified and is happy because they didn’t have to compile their code or execute their script to find them.
- tabular Sometimes, it’s useful to line up text. Naturally, it’s nicer to have the computer do this for you, since aligning things by hand quickly becomes unpleasant.
- vim-puppet Make vim more Puppet friendly!
- vim-fugitive Provides an amazingly deep Git integration for vim.
Also you’ll find a snippets directory with a custom list of snippet for Puppet.
If you work in IT it’s pretty normal in these days to have a computer with at least 4GB of RAM and if you have bought it in the last year probably it has 8GB, this is fantastic to run modern applications that usually require much more RAM than in the past, but this make the use of Virtual Machine on personal computer much more easy and doable.
This open some interesting options in the development cycle of any application or service as now it’s possible to have a development/test machine on every personal computer, as system administrator I’d like that these VM should be as much similar as possible to the production environment, so what’s a good way to manage and distribute Virtual Machines to the developers ?
For what I’ve found around the best answer at the moment it’s: Vagrant.
In this first part I’ll cover the theorical aspect of Vagrant and in the next one I’ll show you some basic command to setup a running environment with it.
Readers would be pleased to know that I have teamed up with Packt Publishing and we are organizing a Giveaway especially for you and three lucky winners stand a chance to win a copy of the book on Puppet. Keep reading to find out how you can be one of the Lucky Winners.