Mercurial, Fabric, Liquibase, Kohana (part 4)

Today I am focusing on making sure all database related stuff from previous parts can be executed by me and any of my teammates on their local machines using Fabric.

Mercurial, Fabric, Liquibase, Kohana (part 3)

My new application is going to require an authentication. I am not looking for anything fancy. For starters the ORM authentication available in Kohana 3.3 will do. I may extend it later. This means that I am going to use database to store user accounts. As I am a big fan of database code versioning I'll be using LiquiBase to do that. So how to go about it?

Mercurial, Fabric, Liquibase, Kohana (part 2)

I will be using Mercurial to keep track of changes to a project. I create a project directory and initialize a Mercurial repository in it:

shell> hg init

I do like to have an option to switch Kohana with new version easily in my projects. To achieve that I unpack downloaded Kohana into kohana directory of my project. I then copy application directory from kohana folder into root of my project, so it is on the same level with kohana directory. The same needs to be done with index.php and .htacess. Structure of my project looks like this after that:

project
  |- application
  |- kohana
  |- .htaccess
  |- index.php

Mercurial, Fabric, Liquibase, Kohana (part 1)

I'd like to to start writing about my usage of these tools, but inevitably I would have to write why I am using those specific tools. So not to return to this later I start with my reasons.

Database documentation

It is so frustrating to guess database structure intention without any information about it. Liquibase has a great feature, which helps to prevent a lot of guessing. Liquibase can generate an html documentation of db. However the documentation is pretty sparse. But be not frustrated, there is a light over there at the end of the tunnel...

LiquiBase - the way to handle a database

I am in a middle of rework of an old script. Whole structure of a solution was cumbersome a lot so I had to step in to correct the stuff. I knew that the script has some data in a MySQL database. It uses few tables in a large db with tens and tens of other tables.