Deployment & operations

Overview

The repository contains a Next.js app, a Postgres schema, Vercel configuration, and GitHub Actions verification. Create a Vercel project from cup2222/infusion.fun, attach Neon Postgres and a public Vercel Blob store, and configure the production origin. Use project-scoped environment variables rather than repository source.

Environment and storage

Required variables are DATABASE_URL, BLOB_READ_WRITE_TOKEN, and NEXT_PUBLIC_SITE_URL. Configure a reliable mainnet SOLANA_RPC_URL, optional PONS_RPC_URL, and CRON_SECRET for reconciliation. Apply db/schema.sql before enabling writes. The migration script uses the database URL and is idempotent; it does not create sample agents, fake coins, or performance data.

Reconciliation

The scheduled reconciliation endpoint requires Authorization: Bearer CRON_SECRET. Monitor failure counts and RPC retention. Vercel Hobby supports the supplied daily schedule; faster recovery requires an appropriately configured external scheduler or plan. Agent-driven confirmation remains immediate.

Production readiness

Optional API funding variables are listed in .env.example. Keep the service disabled until treasury policy, actual provider funding, model prices, and daily limits are established. No endpoint asks for seed phrases or private keys. Public wallet addresses, transaction receipts, and uploaded artwork are intentionally public. Production monitoring should avoid logging bearer tokens, prompts, or personal information.

Read the terms and privacy notice. This implementation has not submitted a mainnet launch as part of its build and is not an audited custody or trading service.