@@@@ KLAXON.WAV @@@@@
This is a booking specific text commit. Don't send this upstream or baby
jesus will cry.
Correcting the POD

`httpd restart` doesn't work anymore, replacing it with the new vernacular.
Git::Deploy::Hook::LoadBalancerCheck; fix typo in output
Support arguments in Git::Deploy::Question::_question
Git::Deploy::Hook::RestartHTTPD: remove booking-specific hooks

Remove hooks that aren't used by Git::Deploy itself, but just by the
Booking hooks. We'd still like to have some example hooks in the
future, but these are all kinda usecase-specific.
Revert "Correcting the POD"

This reverts commit c9a22c6c2c80723d3e61a08d4d97192105178d57.

This is the open source documentation that isn't specific to our site,
httpd restart is a general command, dude is not.
Remove comment for code that isn't there anymore
Code Prettyness: align hash key-value list
Pass GIT_DEPLOY_ACTION down to the hooks

It's now possible to check which action you're in in the hooks, I'm
going to be using this for a new post-start hook to print howto
messages for hotfixes.
Phase Hooks: add a post-start hook

I'm using this hook to print out some instructions about how to do
hotfixes.
shuffling whitespace
make Git::Deploy export get_hook_dir (--show-hook-dir was failing)
whitespace
modeline
Run pre-start hooks *before* creating a status/lock directory

This allows pre-start hooks to fail cleanly which will in turn prevent a start,
hotfix, revert from taking place.

Without this, a failed pre-start hook would leave a lock directory in place but
not a lock file, which made other stuff (i.e. abort) fail miserably.
gitignore: Add TAGS
Revert "@@@@ KLAXON.WAV @@@@@"

This reverts commit 28c40f96af57064ed58ca68ec82551088f3a4509. I'm
going to replace this with a feature that makes custom sync hook fail
messages configurable rather than hardcoding a booking-specific
message.
Add a facility for emitting custom sync error messages

Instead of having a Booking.com-specific sync message add a facility
for specifying custom ones in the config file. Tested with this
monkeypatching to git-deploy:

    my $sync_hook = "foo";
            my $sync_hook_fail_message = get_config(
                'message-on-sync-hook-fail-whale',
                "A) Retry the synchronization hook. You can do this by moving to the root of the repository\n" .
                "   and executing the following command by hand:\n\n" .
                "   \$ {SYNC_HOOK}\n\n" .
                "   which if it succeeds can be followed with a\n\n" .
                "   \$ git-deploy finish\n\n" .
                "   If that doesn't work then you should seek further assistance from sysadmin.\n" .
                "   * NOTE * This is NOT an error in git-deploy itself.\n\n" .
                "B) Inform {SUPPORT_EMAIL} of the failure and any relevant\n" .
                "   output there might be. Please do this even if the manual process works out.\n\n"
            );
            _expand_template_variables(
                \$sync_hook_fail_message,
                {
                    SYNC_HOOK => $sync_hook,
                    SUPPORT_EMAIL => get_config('support-email','maintainer'),
                }
            );

            _tell
                "The syncronization hook has returned failure: $@\n\n",
                "                         *** DON'T PANIC ***\n\n",
                "You will now be dropped into 'manual' sync mode. Please follow these instructions:\n\n",
                $sync_hook_fail_message;

    exit 0;
Tests: fix tests to not test for hooks removed in eaf10d9
README.pod: bump from git-deploy

Updated with: grep -A 9001 ^=head1 git-deploy >README.pod