Moving a Lovable Cloud App to Your Own Supabase Project: Step-by-Step

·2 views

A new guide explains how to migrate an app built on Lovable Cloud to a Supabase project the owner controls. Because Lovable Cloud runs on a Supabase project managed by Lovable, it cannot be linked to a personal account, so the move requires creating a new project, copying the database and files, and switching the app's connection settings. The process covers exporting and restoring the database, which carries user accounts and password hashes, while sessions end and files, secrets, sign-in provider settings and connectors must be transferred manually. The guide advises keeping the old backend running until the new one passes all checks, and deleting nothing in Lovable until verified copies are held.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why IBM's Granite name became shorthand for built-in AI guardrails

IBM's open Granite family of enterprise AI models has become a metaphor for guardrails, with the name meant to evoke durability and structural integrity. The article says Granite models ship with alignment layers, configurable output filters, and safety mechanisms built in during pretraining, rather than added afterward. It draws a comparison to granite's geological formation, describing safety as embedded in the material instead of bolted on. The metaphor reportedly appears in IBM documentation, technical briefings, and Brazilian regulatory discussions on AI governance. The piece also notes that the models support fine-tuning and retrieval-augmented generation while keeping core safety constraints intact.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Freelancers Can Deduct AI Subscriptions and API Costs at Tax Time

Self-employed people can generally deduct AI services they pay for as business expenses, though rules differ by country and a local tax authority or accountant should confirm the treatment. Subscriptions like ChatGPT are typically filed under internet or software services, with service fees also commonly accepted, and the same category should be used consistently across years. For accounts used for both work and personal purposes, only the business-use share should be deducted, based on a documented basis such as periodic review of chat history. Pay-as-you-go API charges usually fall under the same category, with foreign-currency costs converted at payment time. Costs like courses, books, and equipment have their own treatment, and avoiding a catch-all miscellaneous category keeps records clearer.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

agentgc queues heavy builds for parallel Claude Code agents via a hook

A developer describes running several Claude Code agents on one laptop, where simultaneous heavy jobs such as test runs and builds can overload the machine. They built agentgc, a CLI whose Claude Code hook rewrites heavy commands like cargo test or npm run build to run through a queue. By default, a quarter of the logical cores (at least one) run heavy work at once, and the rest wait for a free slot. The hook asks for approval before rewriting commands, with an --allow option to skip that prompt, and it only rewrites plain single commands, not those with shell syntax. The release notes say tests pass on Windows, Linux and macOS in GitHub Actions, but the full flow was only tested by hand on Windows, and unsigned binaries may trigger OS warnings.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Delivered Emails Still Land in Spam and How to Test Inbox Placement

A password reset email can be accepted by an API and marked as delivered while the user still cannot find it, because delivery signals do not show which folder the message reached. Services like Amazon SES separate acceptance of a sending request from delivery to a recipient's mail server, and neither of those events confirms inbox placement. Diagnosing the gap requires evidence from the receiving mailbox, such as a saved copy of the received message. Inspecting authentication results in that copy can reveal issues like SPF and DKIM alignment, though these reports are not independent proof of placement. The guide recommends running controlled seed-mailbox tests while keeping small samples from being treated as definitive guarantees.

0 comments Read more at DEV Community