altera-new-app

Scaffold, configure, and verify a new Altera framework application with PostgreSQL.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/IgorAIvanov/altera03 --skill altera-new-app-igoraivanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altera-new-app
Source: https://github.com/IgorAIvanov/altera03/tree/main/skills/src/altera-new-app
Command: npx skills add https://github.com/IgorAIvanov/altera03 --skill altera-new-app-igoraivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a new Altera application involves a scaffold plus six follow-up steps where silent failures are common: a skipped deno install breaks the build later, a leftover VITE_DEV_URL shows a blank page, and a reused project name collides with a neighbouring app's database, role, and session cookie. This Skill walks the full sequence and verifies the app actually runs, not just that commands executed. ## Core Features & Use Cases - Preflight checks: Validates Deno 2.9+, Docker, project-name pattern, port availability (3000/5173/5432), and name collisions with existing Altera apps before creating anything. - Guided configuration: Edits .env values that must change — PGPASSWORD, BLOB_TOKEN_SECRET, BOOTSTRAP_PASSWORD, ports, and AUTH_COOKIE_NAME — with explanations of why each matters. - Database and schema setup: Brings up PostgreSQL in Docker or uses an existing server, then runs sql:registry, sql:assemble, and sql:publish to build the schema. - Verified launch: Starts the dev servers and confirms a 200 response and working login screen on the Vite port, with a troubleshooting table for common failure messages. - Use Case: Given an empty directory, scaffold a new Altera app named "myerp", bring up PostgreSQL in Docker, publish the schema, and confirm the login screen loads at localhost:5173. ## Quick Start Deploy a new Altera application named myerp in this empty directory using a Docker PostgreSQL container and verify the login screen works.

Frequently Asked Questions about altera-new-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a new Altera application from scratch?

Run deno run -A jsr:@altera/create . in an empty directory, copy .env.example to .env and set PGPASSWORD and BLOB_TOKEN_SECRET, start PostgreSQL with deno task startdb, run deno install, publish the schema with the sql tasks, then start deno task dev and verify the login screen on port 5173.

Why does the Altera build fail with 'Could not load vendor' errors?

The deno install step was skipped before the build. The project's deno.json sets vendor: true, so the Vite preset and Tailwind read framework sources from disk; without vendoring, the build cannot resolve @altera/client files.

Can I run two Altera applications on the same machine?

Yes, but they need distinct project names, ports (PORT, VITE_PORT with VITE_DEV_URL, PGPORT), and BLOB_TOKEN_SECRET values. The template derives PGDATABASE, PGUSER, and AUTH_COOKIE_NAME from the project name, so identical names cause silent database and session collisions.

Why does localhost:3000 show an empty page after starting the Altera app?

While VITE_DEV_URL is set, port 3000 serves only the API; the interface runs on the Vite dev server at port 5173. Open http://localhost:5173/ to reach the login screen.

Why does PostgreSQL authentication fail after editing the .env file?

The Docker container creates the database with the credentials from .env at its first start and keeps them. If you edited PGPASSWORD afterwards, run deno task stopdb and bring the container up again so it reinitializes with the new values.