Set environment variables before the first deploy

You can now add environment variables while creating a project or environment, so the very first deployment runs with the config your app needs — API keys, database URLs, NEXT_PUBLIC_* values — instead of an empty set.

Adding variables during setup

Both the project-create and environment-create wizards now have an optional Environment variables section in the Source & Deploy step. It stays collapsed for the zero-config case, so simple projects are unaffected.

• Add variables as key/value rows.
• Or select Paste .env to import a whole block at once — Velumi parses it and shows what will be added.
• The Review step shows how many variables you've configured before you create.

Copy from an existing environment

When creating a new environment, use Copy from: {environment} to seed it with the variables from an environment you already have — no re-typing keys.

Failed-deploy hint

If a deployment fails and its environment has no variables set, the deployments page now shows a dismissible banner linking straight to the Variables tab, so a missing-config failure is easy to spot and fix.