How to Participate

just a collection of notes at the moment

You may be interested in the Proviso community project, which will extend the efforts of Kalastack with broader scope:

Proviso aims to be an SDK+API to provision platform-independent local VMs for Drupal development. The project seeks to develop an extensible framework and ecosystem for developers to achieve parity with multiple production deployment targets, as well as a one-click installer control panel that makes advanced local development accessible.

You may also be interested in the Terminatur

##Building

as outlined in the readme, you can build the Kalastack with

$ vagrant plugin uninstall vagrant-hostsupdater
$ vagrant plugin install vagrant-hostsupdater
$ vagrant up

but if you run into problems, destroy the box

$ vagrant destroy

then enable vagrant's debugger on *nix with:

$ VAGRANT_LOG=info vagrant up

##Developing with Kalastack run latest installer Fork the github project and check it out locally. Add the original project as a remote. Here we call it "upstream".

$ git remote add upstream https://github.com/kalamuna/kalastack.git

see github documentation for more on this. pull down HEAD of 3.x branch from Kalastack repo.

$ git fetch upstream
# Fetches any new changes from the original repository
$ git merge upstream/master
# Merges any changes fetched into your working files

To test you changes update the vagrant box with new, local puppet manifests:

$ vagrant up

If your local change works, pull, commit it upstream and issue a pull request. If your pull request is merged into the repo you can try out the development version of Kalastack:

$ export KALABOX_REMOTE=TRUE #this will tell vagrant to pull HEAD
$ vagrant up

If you are having problems and want to send error reports to our remote Foreman you can do. This will pull from the latest dev of Kalastack.

$ export KALABOX_REMOTE=TRUE #this will tell vagrant to send reports to the puppet master
$ vagrant up

When a new version of Kalastack is released your changes should be in the puppet server provided they were merged in.

unset your KALABOX_REMOTE or var to switch vagrant back to puppet server mode :

$ unset KALABOX_REMOTE
$ vagrant up

Huboard

currently evaluating Huboard, an experimental agile board integration with github at: http://huboard.com/kalamuna/kalastack/board