turnip | Drupal starter kit , with a focus on developer collaboration | BPM library

First, you'll need the Ruby environment itself so you can install Ruby gems. For Ubuntu (inlcuding 14.04), the easiest way to do this is to use RVM.
If you are using modern web technologies, you probably already have this set up. If not, check out Installing Compass and Sass Across All Platforms. Or, simply:.
Having your Ruby environment setup, you can simply.
Turnip is best installed using Drush. Make sure you have a drush executable in your $PATH and then:. Drush will prompt you to set up the repository and build the base install profile. It will also set up the turnip remote to upstream Turnip. If you haven't set up your Ruby environment as described above, when prompted, you will want to skip building the theme. However, no theme can cause problems, so it's best to get your environment set up before installing Turnip. If you don't build a theme now, you can do it later by calling bin/init-theme from within the project root directory. Add all your newly updated files with git add -A and then commit them. Now is a good time to set up your own remote repository if you plan on using Git for version control (which you should!). (See Step 2 under Manual Setup below). Make a files directory in the shared directory. Customize settings.local.php with your database parameters and any special configurations. Run bin/install for local development.
Turnip is best installed using Drush. Make sure you have a drush executable in your $PATH and then: drush dl turnip drush turnip-init Drush will prompt you to set up the repository and build the base install profile. It will also set up the turnip remote to upstream Turnip. If you haven't set up your Ruby environment as described above, when prompted, you will want to skip building the theme. However, no theme can cause problems, so it's best to get your environment set up before installing Turnip. If you don't build a theme now, you can do it later by calling bin/init-theme from within the project root directory.
Add all your newly updated files with git add -A and then commit them. Now is a good time to set up your own remote repository if you plan on using Git for version control (which you should!). (See Step 2 under Manual Setup below).
Customize my_profile/my_profile.make.
Make a files directory in the shared directory.
Customize settings.local.php with your database parameters and any special configurations.
Run bin/install for local development.
To avoid having to redeclare your default origin each time you pull or push, run your first push as: git push -u origin master
If this site has a production url, you can manually add it to bin/.config on the line PRODUCTIONURL="http://".
Custom modules or features should go in my_project/modules/custom or my_project/modules/features. Any contrib modules put into the .make files will be placed into the appropriate directories automatically.
Turnip assumes you will keep your sensitive database information in an uncommitted (gitignored) file called settings.local.php. Make any applicable changes to settings.local.php.example and save it as settings.local.php.
Either copy all files into a new repository or clone this repository, keeping an upstream origin named turnip:.
Either copy all files into a new repository or clone this repository, keeping an upstream origin named turnip: git clone -o turnip git@github.com:opensourcery/turnip.git foo_project cd foo_project git checkout -b master
Initialize git (if files were copied), and add a remote: git remote add origin git@github.com:foo/bar.git Make sure your remote points to a repository that is set up.
Run bin/make-install-profile to instantiate an installation profile and spin up the Arcturus subtheme: bin/make-install-profile my_profile my_theme "Short name" "Long name"
Customize my_profile/my_profile.make.
Make a files directory in the shared directory.
Copy settings.local.php.example to settings.local.php and fill in the databse parameters.
Run bin/install for local development.
To avoid having to redeclare your default origin each time you pull or push, run your first push as: git push -u origin master
If this site has a production url, you can manually add it to bin/.config on the line PRODUCTIONURL="http://".
Custom modules or features should go in my_project/modules/custom or my_project/modules/features. Any contrib modules put into the .make files will be placed into the appropriate directories automatically.
Turnip assumes you will keep your sensitive database information in an uncommitted (gitignored) file called settings.local.php. Make any applicable changes to settings.local.php.example and save it as settings.local.php.
By building the site out as an installation profile, funcitonality can easily be tracked in commit logs. The Profiler library is used for creating placeholder nodes, users and taxonomy terms, as well as setting variables that don't make sense to commit to feature modules.