Drupal Camp Asheville 2024 - July 12th-14th

From Managed Hosting to Cloud Freedom: Three Pathways to AWS or Digital Ocean

Will Kirchheime
REI Systems
Salim Lakhani

This sessions is about three ways to move your development environments and production hosting to your own cloud provider (like AWS or Digital Ocean). High-level overview of what it takes to migrate from managed hosting to your own cloud providers. We address setup, dev tools, cloud dev and staging environments, scalability, security and release management.

Level Up Your DDEVry

Bernardo Martinez

DDEV provides a powerful suite of commands and tools that often go underutilized. You may have read about some of them, but have you seen them in action?

This session provides a quick overview of DDEV architecture and how it can empower you and developers of all levels to get up and running in minutes.

Building a LAMP Based Web Server in the 21st Century

Kevin Pittman
Georgia Institute of Technology

When selecting a place to host your Drupal site (or any kind of website) you may feel stuck between the many commercial products out there, from Plesk and CPanel to third-party ISP hosting.  There is another option: you can still build your own fully open-source web server in the tradition known as LAMP (Linux, Apache HTTPD, MySQL, PHP).  We'll step through the process of standing up a LAMP ser

Professional Drupal Module Development Tools (Visual Studio Code + DDEV/Lando)

Michael Anello
Looking to set up your local development environment with tools necessary to build top-notch Drupal custom modules? In this half-day workshop, Mike Anello, lead instructor of DrupalEasy's 90-hour Professional Module Development course, will help you set up Visual Studio Code alongside your existing DDEV or Lando installation with all the plugins, extensions, and code quality tools to put you in a position to succeed. Tools covered will include Drupal Coder (phpcs, phpcbf), PhpStan, PhpUnit, and Xdebug. 

Decoupled Drupal Dev on Docker with Docksal Doing the Dirty Work

JD Flynn

When a decoupled project begins one of the hardest parts that I’ve found is setting up a local environment to simulate all the necessary components.  How will the CMS be served? How will the decoupled front end be displayed? What about the dev server for rendering previews? Can I still call it headless or is decoupled the only appropriate word?