Drupal Camp Asheville 2024 - July 12th-14th
In 2024, Google and Yahoo have instituted more stringent email requirements for senders who wish their email to be delivered to Gmail or Yahoo Mail accounts. Failure to meet these requirements is expects to result in email not being delivered.
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.
DoD developed the After Action Review (AAR) as a way to to learn quickly from soldiers' experiences in the field.
Today, AARs have been adapted to allow software developers and security professionals to address issues as they come up with the focus being what can be learned and then put into practice.
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.
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
We all know we should be doing more automation of our software development lifecycle, but getting started can be challenging. Even if you have experience in continuous integration and continuous delivery (CI/CD) automation, learning a specific platform's terminology and idiosyncrasies can be frustrating.
Imagine starting your week with the discovery that all your AWS-hosted photos have vanished. This unsettling scenario became our reality when AWS S3 bucket keys were compromised, leading to the unexpected deletion of essential digital assets.
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?
