 | Hi everyone, After spending a few years at my first developer role I decided to take a year out of work to go travelling in Asia, now I'm back and ready to enter the job market once again. I'd like your help to get honest feedback on my resume before I start applying for jobs. I'm mainly looking for feedback on:
Thanks! [link] [comments] |
© Jeenah Moon/Bloomberg/Getty Images
 | First time posting here. Sharing lerd because it has solid Drupal support and might be useful for folks who want a Podman-based alternative to DDEV or Lando without Docker Desktop, especially on Linux where the usual mac-first tools are awkward. Lerd auto-detects Drupal projects via composer.json, handles the web/ document root, and gives you .test domains, per-project PHP version isolation (Drupal is strict about PHP requirements), one-command HTTPS via mkcert, MySQL or Postgres with one click, and Mailpit for email testing. Drush, Composer, and PHP commands all work through container shims so they pick up the right PHP version per project. Everything runs as rootless Podman containers, nothing touches your system PHP, no sudo required after install. Highlights:
Would love feedback from Drupal devs, especially around Drush integration and module/theme dev workflows. If lerd looks useful, stars on GitHub help a lot with reach. [link] [comments] |
Have an on prem D7 environment and looking to move everything into the cloud (Azure or AWS).
Discussions around the table is approach:
or
Any tips, tricks, or recommendations are appreciated.
© iStock/Rest of World
© Rest of World/iStock
May 4, 21:01 UTC
Completed - The scheduled maintenance has been completed.
May 4, 13:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 2, 13:25 UTC
Scheduled - Start: 2026-05-04 13:00 UTC
End: 2026-05-04 21:00 UTC
During the above window, our Engineering team will be performing maintenance on core control plane infrastructure. Please note that the existing infrastructure will continue running without issue. This maintenance may impact create, read, update, and delete (CRUD) operations in all regions.
Expected Impact:
During the maintenance window, users may experience brief periods of increased latency with the following platform operations:
Cloud Control Panel and API operations
Event processing
Droplet creates, resizes, rebuilds, and power events
Managed Kubernetes reconciliation and scaling
Load Balancer operations
Container Registry operations
App Platform operations
Managed Database creation and scaling
We do not expect any impact to customer traffic due to this maintenance. If an unexpected issue for the control plane arises, we will endeavor to keep any impact to a minimum and may revert if required.
If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
May 4, 15:00 UTC
Completed - The scheduled maintenance has been completed.
May 4, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 2, 12:39 UTC
Scheduled - Start: 2026-05-04 13:00 UTC
End: 2026-05-04 15:00 UTC
During the above window, our Networking team will be making changes to the core networking infrastructure to improve performance and scalability in the SFO2 region.
Expected impact:
We do not anticipate any downtime for Droplets or Droplet-related services, including Managed Databases, Load Balancers, App Platform, and Managed Kubernetes, as this maintenance has been carefully designed and tested to be seamless. In the unlikely event that an undetected misconfiguration occurs, a subset of customers could experience temporary network disruption. We will endeavor to keep this to a minimum for the duration of the change.
If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
May 4, 21:00 UTC
Completed - The scheduled maintenance has been completed.
May 4, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 2, 09:15 UTC
Scheduled - Start: 2026-05-04 13:00 UTC
End: 2025-05-04 21:00 UTC
During the above window, our Engineering team will be performing maintenance on core control plane infrastructure. Please note that the existing infrastructure will continue running without issue. This maintenance may impact create, read, update, and delete (CRUD) operations in all regions.
Expected Impact:
During the maintenance window, users may experience brief periods of increased latency with the following platform operations:
Cloud Control Panel and API operations
Event processing
Droplet creates, resizes, rebuilds, and power events
Managed Kubernetes reconciliation and scaling
Load Balancer operations
Container Registry operations
App Platform operations
Managed Database creation and scaling
We do not expect any impact to customer traffic due to this maintenance. If an unexpected issue for the control plane arises, we will endeavor to keep any impact to a minimum and may revert if required.
If you have any questions related to this maintenance please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket
© iStock/Rest of World
Hey, let's say I initiated new Drupal project locally using official ddev instructions. Smooth and clean experience, all good. Now, what to do next? I would like to start develop - turn off twig and any other caching, enable debugging, ensure that .gitignore is prepare for a composer-managed project, configure config_sync_directory so i can store entire site configuration in a git.
Nothing special I would say - just a normal way of working on a stuff as a developer, while keeping the best practices.
And the question is: Where I can find some official docs so I do not have to use a tribal knowledge or guess whether I configured my gitignore, settings and services files correctly? Where i can read such an infos like why there is a dot in third line of .gitignore, after /vendor.?
Did I missed something or this part is not well documented?
© Mohammed Al Ali/Shutterstock
 | Recently I audited a Drupal codebase containing a lot of custom form code and the author relied upon front-end validation way too often. You always want to validate form submissions server-side as well. I'm posting this because I sense that this change in Drupal 12 may prove impactful for many sites. Check your form validation code! [link] [comments] |
Login
