Latest Blog Posts
Single site content staging with Deploy
This demo shows creating content on a stage workspace then deploying it to live. Once deployed an edit is made on the live workspace and an update is done on stage to pull from live.
Cross site content staging with Deploy
Now with RELAXed Web Services installed cross-site deployments can be done. First replicator users are setup with the permissions to replicate content. These users are added to the Relaxed settings on Drupal 1. A remote is added to Drupal 1 for Drupal 2. The live workspace is updated to set the upstream workspace to Live on Drupal 2. Content is created on Drupal 1 and deployed to Drupal 2. A change is then made on Drupal 2, and Drupal 1 is updated to pull the changes from Drupal 2.
This year I have proposed three sessions for the North American DrupalCon based on the topics I have been working on for the last 9 months.
Please take a look, ask questions, make comments, and share.
Building sites with Composer
If you have been keeping up to date with by blog you will notice I have been working a lot with Drupal and Composer. In this session I will share this knowledge and look from a site builders perspective.
Managing and staging your content
In Barcelona and Mumbai, Dick Olsson and I, presented on content management and content staging solutions. We have been continuing to work on improving these solutions and wish to give an updated session in New Orleans.
Drupal is a CMS, so how can we better manage content?
This session will discuss many of the same topic as the earlier session “Managing and staging your content” however from a much more technical point of view, and with the goal of, how do we get this into Drupal core. Drupal 8 now has configuration management, it’s time we also focussed on content management.
<p>As of <a href="https://www.drupal.org/node/1475510#comment-10817894" target="_blank">1:23pm GMT on Febuary 3rd 2016</a> there are no dependencies in the Drupal 8.1.x git branch.</p>
<p>There was no reason to have them there. It makes the repository bigger, and therefore takes longer to download. <a href="https://github.com/joomla/joomla-cms" target="_blank">No one</a> <a href="https://github.com/laravel/laravel" target="_blank">else</a> <a href="https://github.com/symfony/symfony" target="_blank">does it</a>.</p>
<h2>What does it mean?</h2>
<p>Not much really.</p>
<p>If you download Drupal via the zip file or tarball then the drupal.org packager will run <code>composer</code> so the dependencies will be there for you.</p>
<p>If you submit a Drupal core patch on drupal.org then DrupalCi testbot will run <code>composer install</code>.</p>
<p>It’s only if you clone Drupal 8.1.x or higher directly from git, you will need to run <code>composer install</code> in the Drupal root directory</p>
<p>Top tip: <code>composer install --prefer-source --no-interaction</code> can often be quicker.</p>