<commit_before>deployogi
=========

easy, automatic deployment of webapplications/databases on staging/production webservers using GIT hooks and bash triggers<commit_msg>added README.md<commit_after>Deployogi
=========
Deployogi is a bashscript which enables easy, automatic deployment of webapplications/databases on staging/production webservers using GIT hooks and bash triggers.

Say What?
=========
in other words: putting a new version of a website in production by simply hitting enter.

Why?
====
So teams can deploy many webapplications in one and the same way.
The maintaining-upgrade-test-and-deploy-cycle for many webapplication can be done in many ways. 
Handhacking this process *will* become more and more labourous/specialized as the webapplications mature.

For who?
========
Well not for one-man-banddevelopers, in those cases handhacking is part of the fun!
But in case of a devteam it is the only way to be flexible in scalability of your team.

How?
====
Simply by pushing to a remote git-repository.
Only thing to do once is writing a config-file and optionally some triggerfiles ('on.backup' / 'on.update' e.g.).
Thats it!

Example workflow
================
Lets assume you have at least one application maintainer (who merges gitbranches into staging- and master-branch) and developers
who create feature-branches. 

Requirements
============

* LAMP server
* a webapplication which supports cli-invokation (to configure frameworkrelated variables from the commandline)
{'fraction_non_alphanumeric': 0.08975217682518419, 'fraction_numerical': 0.0, 'mean_word_length': 5.148148148148148, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1706875', 'n_tokens_mistral': 399, 'n_tokens_neox': 378, 'n_words': 189}