Sites using Acquia Search typically have one Apache Solr Core/Index assigned to them, shared across multiple environments. To prevent duplicate search results, the Apache Solr environment is configured in "Read-only" mode on all-but-one of the environments (usually the production site).
This can make it difficult to test new Apache Solr-related features or configurations in the development- or staging-environment and can cause issues when content is not synchronized across the different environments.
This module adds an additional field (ss_ah_environment) containing the environment identifier when indexing content, and limits returned query results by that field. This essentially divides an index into sections per (Acquia Hosting) environment.
Installation
Enable the module. The module does not require any configuration.
Drawbacks
By enabling this module, each environment (local, development, staging and production) stores all documents within its own section of the index, causing the index to be larger (typically 2 - 3 times as big) then would be the case if documents would only be indexed from one environment.
Past is an extended logging framework, designed to log and later analyze complex data structures to a pluggable backend.
It can record watchdog events (and be a watchdog module replacement). Also it can capture uncaught exceptions with backtraces and circumvent PHP limitations in error handling with a shutdown handler to capture all possible application errors. It can even scan PHP error.log files for missing pieces.
Another typical use case for past is logging communication between one or multiple services, where data is received, processed and forwarded.
A single log message is called an event, which can have multiple attached arguments, each argument can be a scalar, an array, an object or an exception. Complex data structures like arrays and objects are stored separately so that they can be searched and displayed in a readable way, those rows are called "(event) data".
Features
Procedural and object oriented interface for logging events
Attach any number of arguments to a single event
Pluggable backend. The current default backend is a database/entity based backend, a simpletest backend is additionally provided that allows to display events as debug output
Each element in an array or object is stored separately to be search and filterable
Tired of complicated local environments that are pain to setup and are always inconsistent between your machine, your co-workers machines and the live environment?
Druidbox aims to solve this problem by creating perfect environment automatically with just few commands. It uses Vagrant for virtualization, and Puppet for managing and keeping the installation consistent across all your environments.
Some of the installed tools include:
Apache
Mysql
Nginx
Git
Pear
PHP-FPM
Drush
Xdebug
Node.js
MongoDB
Capistrano
Less
.. And many others.
The project(and installation instructions) lives in Github for now and is in development phase, please come back later for detailed info.
CREDITS
The project is developed by Roni Kantis and sponsored by Druid. Contact us for all Druidbox consulting and customization, as well as your other Drupal-needs.