I work with Drupal content management framework and sometime ago I started using vim as my main text editor. Out of the box vim does fantastic job but we can customise it by installing vim plugins.

As you may know there is a project called vimrc on the Drupal website that provides detailed instruction how to make vim to support Drupal development. I wrote two articles about vimrc: first one provides summary of steps required to instal vimrc, second one provides overview of all components that vimrc is made of.

I used drush to instal vimrc files but I have discovered since that different method that makes use of Vundle - using Vundle is easy please check for instructions on the GitHub  project's page.

I am not going to write tutorial how and what you need to do in order to write module. If you want to learn this I am sorry but you are in a wrong place. Instead this is about the process that people who use Drupal should be using when thinking about developing new module. I was inspired but the article when should I create a new drupal module - it is very short and you may want to read it in full.Most of people who use Drupal to run websites they go through the same or similar steps when it comes to find module to provide new option. Please check diagram Drupal module decision and I bet you will find it very familiar with what you do or almost exactly what you do already - at least it describes the steps I usually take. I am glad that I came across this article and diagram - finally someone created proper flowchart that I will be using and sharing if neede. Good work.

I was looking recently at options to set up a simple shared Git repository for one of the web projects I worked on.

My initial requirement was to make this work using local Ubuntu users and groups (I am aware of tools that can manage Git users and groups better but did not have time to investigate this further at that time - I use serevice provided by Bitbucket), and users would be able to push and pull over SSH (that was running on the machine already) between theirs local development repository and remote main repository.

Below I give steps for two scenarios that can be used to create Git shared repository for a project. I tested both and they worked for me well.

Create new empty shared Git repository

Steps cover:

I recently had to make the same change on multiple web servers - all configured in the same way and running Ubuntu. My work colleague suggested me to use tool called ClusterSSH. According to documentation: "This tool is intended for (but not limited to) cluster administration where the same configuration or commands must be run on each node within the cluster.  Performing these commands all at once via this tool ensures all nodes are kept in sync.".

I provide below steps how to install and configure this tool on Ubuntu 12.04LTS desktop.

Installing ClusterSSH:

1. sudo apt-get update
2. sudo apt-get install clustershh

Basic use of ClusterSSH: