The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

config(), state() and settings()

Submitted by nk on Wed, 2013-01-09 03:30

In Drupal 7 one could store every random thing not having its own table with variable_set and retrieved it with variable_get and life was simple. There was the $conf variable in settings.php which allowed an easy override. This worked well... until you wanted to copy variables from one server to the other. Or translate them. In Drupal 8, most variables have moved to config() and are still overrideable by $conf. There are a few exceptions.

Drupal 8 progress from my / MongoDB perspective: update #11

Submitted by nk on Mon, 2013-01-07 20:10

Most importantly: we added static caching to the configuration management system. This paves the way of further speedup by utilizing cache_get_multiple instead of loading each object one by one. While Drupal always had the capability to override certain variables in settings.php this is now much nicer and even has its own little API, settings()->get(). The separation of these settings necessary for bootstrap versus the CMI overrides was badly needed. Also, the new Entity Query system now has relationship support (that has been a frequent request).

Automated git pull in a more protected environment

Submitted by nk on Fri, 2012-12-21 20:17

Almost exactly a year ago I wrote about automating git pull from github. I found myself in an environment where a) I wanted to do this b) PHP had been set up so that git pull didn't work. inotifytools to the rescue. First, write a password-like filename (see the old post) PHP script like this:

file_put_contents('pull/git', '');

Then write a bash script:
cd ~/public_html
while inotifywait -qre close_write pull
  git pull

Drupal 8 progress from my / MongoDB perspective: update #10

Submitted by nk on Wed, 2012-12-12 22:17

I have changed course and speed seemingly because now we are so beyond tresholds that feature patches can't get in. So we are in bugfix mode and I have chosen performance ones because those will help in a lot of ways: it will kill a lot of majors and criticals and also speed up testing which helps development overall. Also, the EntityQuery relationship patch relies on converting everything to the new Entity API and that can't happen if it's slow.

Drupal 8 progress from my / MongoDB perspective: update #9

Submitted by nk on Fri, 2012-11-30 06:07

Finally the kernel work is complete: right after settings.php is read, the compiled service container is read and used and there is no other service container being used (while I worked a lot on the early part the previous weeks, this week was mostly the One Container To Rule Them All patch). This means MongoBundle can override everything in the service container easily.

Drupal 8 progress from my / MongoDB perspective: update #8

Submitted by nk on Wed, 2012-11-21 06:16

Another week, another kernel patch. This one moves the kernel initialization to very, very early in the bootstrap process, just after settings.php is read. So, the MongoBundle can override everything easily. Great! There's a patch in the queue which I will turn my attention to once this is in which puts the database service in the kernel. More on this a little later.

Drupal 8 progress from my / MongoDB perspective: update #7

Submitted by nk on Mon, 2012-11-12 22:39

The new DrupalKernel patch is ready. This will unify the bootstrap and the "real" service container and compile them to disk. Very important for us. Also, I had a rift with another developer for too long but in this issue we finally managed (although it's visible we both struggled) to work together and get to an agreement. I am very hopeful this trend continues.

Drupal 8 progress from my / MongoDB perspective: update #6

Submitted by nk on Mon, 2012-11-05 06:29

So Views and Twig are both in Drupal 8 alongside with a configuration import and an entity translation UI. Big, big progress in general. On my end, EFQ v2 has been committed. Now I am doing a number of things in parallel: one, I am rewriting the batch API and have buy in from Crell, bojanz and yched (and I think berdir is OK with it too) so I expect that to get in once it's more completed. We have decided on not supporting "call me again" jobs, just clean, explicit job creation. A new queue operation seems necessarily -- which is move to the end of the queue.

So you want backwards compatibility?

Submitted by nk on Thu, 2012-11-01 02:16

The comment property on the node property is being refactored into a field. Let's pretend -- just because it's a great example not because we want to postpone it -- this happens during Drupal 9! Modules using $node->comment break but modules using $node->get('comment') don't. Modules running SQL queries against {node}.comment break but modules running entity queries with entity_query('node')->condition('comment', 1) do not.

How does the compilation of the Dependency Injection Container to disk affect hosts?

Submitted by nk on Mon, 2012-10-22 22:52

The Dependency Injection Container is now written to disk. When there is no container file available then the DIC is compiled and if the storage backend is writeable then it is written to disk. By default this is written in a tricky (slightly slower but more secure) way into the public files directory.