Delta logger

Component ID

2224577

Component name

Delta logger

Component type

module

Maintenance status

Development status

Component security advisory coverage

not-covered

Component created

Component changed

Component body

UNDER CONSTRUCTION, pre-alpha version [contributors needed, proven concept]: Light module to help especially small projects to fast and easily deploy (small-medium) changes between environments the traditional way:
- deploy new/updated PHP files
- run database (SQL) update scripts
- done!

There are some conditions for this to work 100%, but from my experience, there are many Drupal projects run this way:
- the 2 environments (the Drupal project in this 2 environments) have to be exactly the same when you want to start making changes (to have the same IDs etc); unless sure, this usually means: take the full dump from PROD, put it in DEV, and start making changes
- only one Drupal developer at a time, or taking extra-care when multiple-developers; when working in team with multiple local instances, it needs even more attention and may not be suitable [to be tested]
- if you want to apply changes to content as well, make sure the content you want to change is either frozen in the next environment you wish to deploy to, or blocked from editing (so this content doesn't change in between)

Advantages over Features and others: I will not go into cons of already well-known modules and methods, if anybody (like me) is looking for an alternative, it's obvious there are reasons (and boy, are there many).

Disclaimer: this module is only started (but already reaching it's purpose with some manual work; tested few times and worked). Unfortunately I do not have much time to finish it nor the best Drupal knowledge to make it perfect. I only had a few Drupal projects for which I felt the need to look for this approach and I would like to propose it to more Drupal savvy users in order to check its value or non-value.

How to already use it the way it is now (pre-alpha):
- install the module as usual
- add the Delta logger block as the last one in the Page bottom region (there is a todo to change this approach..)
- try to do some things in your application
- you will notice in the Delta logger block you'll have all page requests list of queries (relevant queries, NO selects, cache, etc), but there is no download button yet, so if you want to deploy it to the next environment, go to the database, delta_logger table, get all (needed) queries and just run them to your next environment

TODO things:
- of course, the get (download) process of an SQL file including the selected groups of queries to be deployed to the next environment; per groups and per tasks
- of course, the deploy control/submodule, to be activated in the next environment in order to upload the SQL file of queries updates
- permissions for the 2 above
- viewing, selecting and excluding queries inside a group
- tasks management, for easier activities management
- live setup: current task + preselect for deployment by activating an "ON AIR" like button
- security checks
- put the delta logger control at the end of the HTML output, not as a block
- real-time refresh, by ajax, to auto-include any background ajax requests update queries in the user' current screen
- better filter relevant queries by testing

HELP NEEDED: as I have little time to none to go any further with this, I'm hoping for Drupal community to pick this up and go further with it or drop it if not valuable (why not?).

Later:: As I have limited network connection or a stupid firewall somewhere, I will git upload it later. For the moment, please get it from here: http://s000.tinyupload.com/index.php?file_id=72315894702937229548