Just got a message from a client offering $5 per page for Drupal implementation work. He said: "How about $5 per page for Drupal implementation? All our work is standard, so working with us is hassle-free." https://preview.redd.it/iyy1ffb98pwf1.png?width=518&format=png&auto=webp&s=baa315d73c480e120f70a0479d2e459f51297727 Honestly, $5 barely covers the time it takes to set up a basic Drupal structure, configure fields, and handle theming—let alone handle revisions or testing. Curious to hear from others: how do you deal with clients undervaluing Drupal or CMS development work? Do you politely decline, try to educate them about fair pricing, or just move on? submitted by /u/VishalYadav-09 [link] [comments]

Oct 22, 17:12 UTC
Resolved - The issue impacting App Platform deployments has been successfully resolved. Users should no longer encounter delays during the build phase or have deployments getting stuck. All services are now confirmed to be stable and operating normally.

We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket for further analysis.

Oct 22, 16:58 UTC
Monitoring - Our Engineering team has implemented necessary changes to address the issue impacting both new and in-progress App Platform Deployments. Our team is currently monitoring the situation. Users should now notice improvements in deployment performance.

We appreciate your patience. We'll update once the issue is confirmed to be resolved.

Oct 22, 16:40 UTC
Investigating - Our Engineering team is currently investigating an issue impacting both new and in-progress App Platform Deployments. During this period, users may notice app deployments getting stuck in the build phase or even delayed builds. In some cases, builds may even fail shortly after retries are exhausted.

We apologize for the inconvenience caused and appreciate your patience while we work to resolve this issue. We'll update once we have more information.

Tolar Grande, a windswept settlement perched at 11,500 feet above sea level in northern Argentina, once received little more than a trickle of visitors. Then, in the late 2010s, hostels...

© Anita Pouchard Serra for Rest of World

Oman’s dream for a spaceport sits in a swath of desert overlooking the Arabian Sea. If all goes according to plan, three separate complexes here will launch everything from small...

© Etlaq

submitted by /u/iacchi
[link] [comments]

Oct 21, 05:41 UTC
Resolved - Between 08:00 UTC and 22:53 UTC, an issue with an upstream provider affected multiple DigitalOcean services, including SMS-based 2FA (causing code delivery failures), Docker Hub-hosted images (impacting Managed Kubernetes and App Platform deployments), and SnapShooter backup jobs. The issue has been resolved, and all services are now stable and operating normally.

We appreciate your patience throughout this but if you continue to experience any issues, please create a support ticket from within the Cloud Control Panel for further analysis.

Oct 20, 10:21 UTC
Investigating - As of 08:00 UTC our Engineering team is investigating an issue affecting multiple DigitalOcean services due to an incident with an upstream provider. As a result, users attempting to log in using SMS-based 2FA may experience problems receiveing codes and complete authentication. Images hosted exclusively on Docker Hub may also be temporarily unavailable, impacting deployments on DigitalOcean Kubernetes (DOKS) and App Platform.

Additionally, the users leveraging SnapShooter for serverless backups may encounter failures in backup jobs as well. We're now seeing signs of recovery, and most of the requests should be succeeding. We will continue to monitor closely to ensure full service restoration and will share an update as more information becomes available.

Inside a multistory office building in Manila’s financial district, around 60 young men and women monitored and controlled artificial intelligence robots restocking convenience store shelves in distant Japan.  Occasionally, when...

© Eduardo Luzzatti for Rest of World

submitted by /u/JumpinJackHTML5
[link] [comments]

submitted by /u/mherchel [link] [comments]

The resale value of electric vehicles is collapsing worldwide, hurting private owners and fleet operators. The crisis became especially apparent when BluSmart, India’s pioneering all-electric ride-hailing service, collapsed in April...

© Rest of World/Getty Images

Oct 17, 04:28 UTC
Resolved - Our Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.

Oct 17, 03:56 UTC
Monitoring - Our Engineering team has implemented the fix to resolve the IPv6 networking issues in multiple regions. Users should no longer have issues connecting to via IPv6 to their Droplets.

We will continue to monitor the situation, and we will post an update once we've confirmed complete resolution.

Oct 17, 02:52 UTC
Identified - Our Engineering team has identified the issue and are implementing a fix. Our team has resolved the IPv6 connectivity issue in FRA1 and are monitoring the situation.

In addition, it was discovered that the NYC1, and SFO2 regions were affected by this issue as well, and our team is currently working to resolve the issue in those regions. To summarize, users in the regions of AMS2, SGP1, NYC1, and SFO2 may still experience connection issues via IPv6.

We are rapidly working on a fix. We will share more information once available.

Oct 17, 00:44 UTC
Update - While investigating this issue, our Engineering team has noticed that the issue is occurring in SGP1 as well. Users in SGP1 may also experience IPv6 connectivity issues at this time.

We are working to resolve this issue as quickly as possible. We will post updates as soon as we have more information.

Oct 17, 00:19 UTC
Investigating - Our Engineering team is investigating an issue affecting IPv6 connectivity in FRA1, and a small subset of users in AMS2. At this time, users may experience issues connecting to IPv6-enabled resources.

We apologize for the inconvenience and will share an update once we have more information.

submitted by /u/Nirabat
[link] [comments]

In February 2023, half a year or so before I visited, a couple of Chinese ships cut two domestic undersea cables running out from Taiwan’s main island. One of these,...

© Taiwan Coast Guard via Getty Images

submitted by /u/Far-Comfortable4462
[link] [comments]

The Secret Login Module allows users to log in through a custom URL defined in the Drupal configuration. When the custom URL is set, a secure tokenized URL is also generated. Users can log in using both the custom URL and the token. This feature is useful for quickly accessing an admin or other user account on a Drupal site without requiring a username or password. Features Allows administrators to define a custom URL in the configuration for all users. Allows administrators to define a custom URL in the configuration for all users. When this URL is accessed, the user is automatically logged in as an administrator along with another assigned role on the Drupal site. The Module also provides a one-time login URL token for a configured user, along with a button to enable or disable the functionality. The token URL is valid for one hour, after which a new token is automatically generated. It also provides a search functionality by username and email, which helps in quickly finding a user — especially when there are hundreds of users on the Drupal site. When the URL token is set in the module configuration, it appears in green, indicating that it is ready to use This module is designed to facilitate easy user login through a custom URL specified by the administrator in the configuration settings. submitted by /u/VishalYadav-09 [link] [comments]

Oct 15, 14:25 UTC
Resolved - Our Engineering team has resolved the issue affecting the creation of NVDIA GPU nodes on new Kubernetes clusters. Users will no longer encounter issues when creating NVDIA GPU nodes on new Kubernetes clusters.

If you continue to experience any issues, please open a support ticket. We sincerely apologize for the inconvenience caused and appreciate your understanding.

Oct 15, 12:18 UTC
Identified - Our Engineering team has identified the issue affecting the creation of GPU nodes on new Kubernetes clusters. Users may continue to experience difficulties when attempting to create GPU nodes on new Kubernetes clusters.

Our team is actively working to resolve the issue and will provide an update as soon as we have more information. We sincerely apologize for the inconvenience and appreciate your patience.

Oct 15, 11:29 UTC
Investigating - Our Engineering team has identified an issue impacting creation of GPU nodes on new Kubernetes clusters. During this time, you will not be able to launch a new Kubernetes cluster with NVIDIA GPU nodes. Existing workloads are not impacted. We apologize for the inconvenience and will share an update once we have more information.