Skip to main content
11
results
Andrew Fletcher
Recently, I encountered an issue where my local Docker environment refused to connect to AWS S3, although everything worked seamlessly in AWS-managed environments. This challenge was not just a technical hurdle; it was a crucial bottleneck that needed resolution to ensure smooth Drupal deployments across various AWS environments (dev, staging and production). Integrating AWS S3 into a local Docker container running Drupal 10 is more than just a technical setup; it’s a transformation that will...
Andrew Fletcher
The error you're encountering indicates an issue with the ffi gem during the...
Andrew Fletcher
The issue of over 300 simultaneous database connections in the context of AWS...
Andrew Fletcher
Logging into the server, and there are packages to be updated.  You know...
Andrew Fletcher
Working in an AWS ec2 environment, my goal is to access the server via...
Andrew Fletcher
Working on a decoupled React / Drupal 9 site. Aim: Adjust the output of curated content for the Work Resources page.  So the icon is displayed with a path.  Enabling React developers to select whether to use the image or icon. Tools Drupal 9.4 React     Currently, the JSON output  { "id": "content_reference", "title": "Forms", "summary": null, "columns": "3", "cta": { "text": "View all", "href": "https://www.google.com/" }, "content": [ ...
Andrew Fletcher
How to make React calls on a Drupal 9 backend site using the search...
Andrew Fletcher
This code is from Drupal 9 back-end for a React front-end via REST API. Working...
Andrew Fletcher
Getting Started with Cocoapods Installation Built with Ruby, Cocopods is...
Andrew Fletcher
You would have come across a URL string that appears...
Andrew Fletcher
Today while in Terminal, I ran a regular script pod update.  However, this time I received the following error [!] CDN: trunk URL couldn't be downloaded: https://raw.githubusercontent.com/CocoaPods/Specs/master/Specs/d/a/2/Alamofire/5.1.0/Alamofire.podspec.json Response: Timeout was reachedI read on GitHub that it could be a cache issue, so I ran: sudo rm -rf ~/.cocoapods/repoNo change. Instead of attempting a pod update, I changed the command to pod install.  Worked a treat....