Urgent.News

What's breaking now, across thousands of outlets.

Tech

Project LifeOps (Part 5): 24/7 Zero-Cost Cloud Deployment ($0/month), Mobile Optimization, and PWA

We have arrived at the grand finale of our engineering series. Across the four previous installments, we designed the database architecture and FastAPI backend , crafted the Glassmorphism Dark Mode React interface , built the interactive fitness, reading, cinema, and Kanban modules , and developed the in-memory Word and Excel reporting engine . Yet in software development, a sobering pattern…

In our concluding segment of the engineering series, we demonstrate a groundbreaking, cost-free approach to deploying full-stack applications. This final installment showcases the full LifeOps project, which includes a production-ready cloud topology, a seamless mobile experience, and an installable Progressive Web App (PWA).

1. Production Cloud Topology ($0/month): To ensure continuous availability without any ongoing expenses, we leverage the most generous cloud free tiers available. The client device uses a web browser or an installed Progressive Web App (PWA) accessible via https://datalaria.com/apps/lifeops/. The front end is served through Netlify Edge CDN ($0/month) with Vite build, Rollup code splitting, and transparent proxy rewrite under the Datalaria domain.

The backend runs on Render.com Web Service ($0/month), featuring FastAPI + Uvicorn container, JWT bearer tokens, HTTPS REST calls, anti-DoS rate limiting, and strict CORS. The Supabase Cloud ($0/month) provides a managed PostgreSQL database instance, isolated schema, and cryptographic JWT session validation.

1.1. Vite Bundle Optimization (vite.config.js): To guarantee sub-second initial loads, especially on mobile networks, we configured Rollup manual chunking. This separates stable external dependencies (vendor-react, @supabase, and vendor-libs) from dynamic code, allowing browsers to cache vendor libraries permanently. When updates occur, users only download lightweight changes.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I tried to check if our new blockchain tools were being used. The tool that would have told me was also silently broken — and so were two other things.

The tool I built to check if anyone used our API was itself silently broken — and so were two other things security #cloudflare #webdev #serverless Yesterday I shipped three new endpoints (a Cosmos…

  • Three new blockchain tools deployed, including Cosmos SDK decoder and EVM sanctions checker
  • Four separate bugs caused by silent failures, requiring manual checks to detect

The configuration we changed in June arrived one pod at a time in August

A support ticket said our dispatch emails were going out twice. Not always, not to any customer we could pick out, and never while we watched.

  • Configuration change from ten to two minutes occurred in June
  • Node pool upgrade in August caused mixed lease durations
  • Annotation and metric implementation resolved configuration issue

OPPO A7 Pro Series Launches In Malaysia

OPPO has officially launched the A7 Pro Series in Malaysia, comprising the A7 Pro 5G and A7 Pro Max 5G. Both models target the mid-range segment, with large-capacity batteries and ergonomic designs…

One new label multiplied our metrics by every order we take

On a Friday afternoon a colleague added a label to a counter so he could follow one customer's orders through a queue. The label was the order id.

  • A single label exponentially increased metrics with every order
  • Label review took only four minutes due to brevity
  • Failure caused metrics server to restart in a loop

Bedrock AgentCore Runtime: Multi-Model Migration from ECS to Managed Orchestration

AWS published a migration guide showing how to move a production healthcare agent from self-managed ECS containers to Bedrock AgentCore runtime.

  • AWS provides guide for migrating healthcare agents from ECS to AgentCore runtime.
  • Preserves triple-model orchestration (triage, diagnosis, treatment planning) during migration.
  • AWS assumes responsibility for state persistence, model routing, and vector retrieval in AgentCore.

More from Saturday 19 September →