I wrote A First Timer's Guide to DrupalCon two years ago, and 99% of the advice in that post is still relevant. I've been preparing my presentation DevOps for Humans: Ansible for Drupal Deployment Victory! for a few months now, and since DrupalCon is less than a week away, I thought I'd take a few minutes to supplement the earlier post:
In the presentation, I'll basically be covering how Server Check.in uses Drupal and Node.js to deliver a simple, fast, and stable server monitoring service. During the course of the presentation, I'll touch on why and how Server Check.in was built, how Ansible is used to maintain the infrastructure, and the effectiveness of lightweight marketing, blogging, and 'low end box' servers.
Join me and many JS developers in St. Louis on May 15, and after the presentation, we'll hack on some of the things mentioned in the presentation!
I'm also hard at work on my DevOps for Humans: Ansible for Drupal Deployment Victory! presentation, which I'll be giving at DrupalCon Austin 2014. I hope to see you there! (Slides from both presentations will be posted online after the respective events).
Drupal 8 brings a lot of changes. Many standby contributed modules are now included with Drupal Core, and many small changes add up to the most exciting Drupal release yet! This presentation guides you through many of the biggest changes, highlighting how Drupal 8 will accelerate your web development and provide tools to make Drupal the best content management platform on any device.
View the slideshow below, or follow the links at the bottom of the post to view the full presentation and video.
Links for full slideshow/video:
This week, the DrupalCon Austin sessions have been posted, and I'm thrilled to have one of my session submissions (in the DevOps track) selected: DevOps for Humans: Ansible for Drupal Deployment Victory!.
The session will go over how Ansible can be used to realize faster, easier, and more successful Drupal deployments, as well as Ansible's ability to make sure that every environment is 'like production', so you don't ever have surprises when you deploy code to its final destination.
If you're interested in building a DevOps culture for your company or consultancy, or if you're already using tools like Puppet or Chef, and want to see what Ansible might offer (YAML and Twig-like template syntax (Jinja2), for starters—just like Drupal 8!), please join me for the session at DrupalCon. The session will cover some of the material I'm writing about in my book-in-progress, Ansible for DevOps.
St. Louis is getting ready for its first-ever DrupalCamp! On April 26, 2014, DrupalCamp St. Louis will open up with a keynote by Brad Nowak, a Business Development Manager at Palantir. The Camp will have sessions covering a variety of topics, like Drupal 8 and how your business can benefit from Drupal's flexibility. It will be held at Washington University's West Campus in Clayton, MO, just a few blocks from a MetroLink station and only a few minutes away from Downtown St. Louis!
Online registration is open already, and for the next couple of weeks, earlybird registration is only $15! For that tiny fee you get:
- A free lunch from Lywelyns
- An snazzy t-shirt
- A full day's worth of Drupal learning from some great Drupal users and developers in St. Louis and the midwest
- A fun after party paid for by our excellent sponsors
Space is limited, so register early to guarantee a spot at the first DrupalCamp in the region!
Also, if you're interested in speaking at the Camp, please submit your session; we'd love to hear about sites you've built, new things in Drupal, business uses of Drupal, project management, site building, etc.!
Using one Apache Solr search core with more than one Drupal website isn't too difficult; you simply use a module like Apache Solr Multisite Search, or a technique like the one mentioned in Nick Veenhof's post, Let's talk Apache Solr Multisite. This kind of technique can save you time (and even money!) so you can use one Hosted Apache Solr subscription with multiple sites. The only caveat: any site using the solr core could see any other site's content (which shouldn't be a problem if you control all the sites and don't expose private data through solr).
There are two ways to make Apache Solr Search Integration work with Domain Access (one of which works similarly to the methods mentioned above for multisite), and which method you use depends on how your site's content is structured.
Solr Search with Domain Access - Siloed Content
If the content you are indexing and searching is unique per domain (just like it would be unique per multisite Drupal instance), then you can set up Domain Access to index content with a different Apache Solr hash per site, like so: