Urgent.News

What's breaking now, across thousands of outlets.

Tech

My OCI sandbox factory now installs on a Free Tier account, with no card

Every time I showed people the thing I built — a chat that spins up Oracle Cloud sandboxes and deletes them when their time is up — the reply was the same. Nice, but I would need a paid tenancy and an admin to try it, so I won't. That was fair. So I made a Free Tier edition. Pick Edition: free on the install form and it runs on an Oracle Cloud Free Tier account with no payment method attached ,…

A chat application that creates and deletes Oracle Cloud sandboxes has been adapted for use with a Free Tier account, eliminating the need for a paid tenancy or payment method. The Free Tier version runs on Oracle Cloud resources that are part of the Always Free offering, which includes an Autonomous Database, NoSQL tables, object storage, and containerized applications.

The system utilizes an Always Free Arm VM with 2 OCPUs and 12 GB of memory, and an assistant API that uses Google Gemini's free key from AI Studio instead of OCI's Generative AI. The factory does not support certain features like Kafka, Functions, Data Flow, Data Catalog, Queue API Gateway, and extra Container Instances, as these are not included with the Always Free tier.

The factory allows only one database per tenancy, and Always Free capacity is shared, meaning resources can become unavailable during peak usage. To install the Free Tier edition, users must launch a Resource Manager stack in their Oracle Cloud region, which takes approximately 15 minutes. The repository and a "Deploy" button are available on GitHub for those interested in exploring the setup process.

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

Wired n8n to Ollama and the MCP Tool — and Hit Almost Every Wall on the Way

n8n running as a container is a decent stand-in for "how would a real automation platform actually call this stuff". Everything up to now has been me calling things directly.

  • n8n container successfully called Ollama integration initially.
  • MCP tool caused cross-filesystem, cross-OS compatibility issues.
  • Mislabeled endpoint field corrected network connection issue.

I keep a public list of things that do not work. It is my best asset.

There are two kinds of documentation for people building autonomous agents. The success writeup, which tells you what worked and why you should do it.

  • Maintaining a failure list is more valuable than documenting successes.
  • Failure information is lost when the person moves on, unlike published data.
  • The failure list creates credibility and attracts readers willing to pay for verified data.

Cheap Node.js Summarization API: Split Long Sales Text with Token Counts

The quality-versus-latency choice should be made before a summarization request, not after a salesperson is staring at a blank CRM record.

  • Node.js API splits long sales transcripts into manageable chunks
  • API maintains speaker turns and key details during summarization
  • Pipeline offers brief and detailed output modes with token count caps

More from Wednesday 30 September →