Amy Parker, Director of Acquia U joins Mike Anello and Ryan Price to talk about the relaunch of Acquia U, as well as the partnership between DrupalEasy and Acquia U. Drupageddon (or is it Drupalgeddon?) is discussed, along with our picks of the week.
- Professionally-Trained, Community-Oriented, Drupal Career Online Students Ready for Work
- Drupal Career Online Spring 2015 begins February 10
- Stay for the Community by Greg Dunlap (heyrocker).
- Your Drupal web site has a back door
- 5 commands that could help you to survive Drupageddon
- 7 Things to Know about the Drupal Security Issue
- Learning from hackers a week after the Drupal SQL Injection announcement
- Drupageddon - Updating to Drupal 7.32 is not enough, your site may already be hacked!
- Shields Up!
- What We Are Seeing With Drupal SA 2014-005
Picks of the Week
- Mike - Paragraphs module by Jeroen Bobbeldijk (jeroen.b).
- Ryan - Ryan’s Sandbox - CalendarLink and ExpertDate
- Drupal 8 Migrate in Core virtual sprints every Wednesday from 7-9pm EST on #drupal-migrate
- BADCamp - November 6-9, 2014.
- If you're interested in career opportunities or learning more about Acquia University, we will be at BADCamp, Baltimore DrupalCamp November 7th, and DrupalCamp Ohio on November 14th and 15th.
Follow us on Twitter
Drupal Way by Marcia Buckingham (acmaintainer) (vocals, bass and mandolin) and Charlie Poplees (guitar). The lyrics by Marcia Buckingham, music by Kate Wolfe.
- Why doesn't Drupal offer an auto update feature like Wordpress?
- Creating Drupal Configuration in Code Using CINC with Scott Reynen - Modules Unraveled Podcast
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or suggestions for new sound effects for next week’s podcast. If you'd rather just send us an email, please use our contact page.
I maintain a large, high-traffic site, and I use Jenkins/Phing to deploy code updates from my GitHub repository. It basically just gets a new copy of the code from the repo, copies it to the server in a new build directory, and then Phing (among other tasks) deletes the symlink to the previous build and re-creates it pointing to the new build directory. This made it very easy to address this issue, because once I committed the change, I just had to deploy it and I had a clean codebase. This meant that if there were any files inserted onto the system (fortunately there weren't), they were rendered moot since they were no longer accessible from outside the server.