Connect what your app needs

3 minute read · Projects & Git

An app may need a database, a mail receiver or an API. Connect those resources once, then let the project reuse them without copying passwords into each conversation.

• Set the right context
• Keep changes deliberate
• Connect a resource to the app that uses it
• Review environment changes
• Diagnose a resource mismatch

Set the right context#

Open the project settings and check its folder, startup command, tests, build command and preview address. Choose the intended named environment: local, staging, production or another configured environment. A name helps you recognize a target; it does not grant permission to change it.

The environment editor manages the project’s environment-file values. Saved connections can supply the resources the app needs. Supported Vercel integration can discover projects and pull environment values through an authorized saved provider connection.

Keep changes deliberate#

Begin with local resources while building the first version. Before a database write, remote command or deployment, confirm which environment and saved connection will be used. Ask the agent to explain the proposed action when the destination is unclear.

If the app cannot connect, compare the selected resource, host/port and running service. Read the specific error without publishing the credential. Fix the intended configuration instead of creating duplicate connections until one works.

Learn to open the database, capture a test email or check before publishing.

Connect a resource to the app that uses it#

Suppose Small Stories uses a local database and sends a welcome email. Save the local database connection in Database and create or select a development SMTP resource. Associate the appropriate resources with the project environment, then configure the app's environment file through the project editor or an authorized agent action. A saved Vortex connection and the app's own environment file are related configuration, not the same storage location.

Use recognizable names such as Small Stories local and Small Stories staging. Before asking an agent to inspect data, name both the project and environment. Never assume that switching the visible environment automatically copies data, applies migrations or makes production safe to modify.

Review environment changes#

1. Confirm the intended environment and the file or saved resource being changed.
2. Enter private values through the credential/environment UI, not an ordinary conversation.
3. Save and inspect any error. Preserve a working configuration before replacing several values at once.
4. Restart only the project process that needs the new settings, if its framework requires it.
5. Verify the connection through a small request, query or captured development message.

Vercel integration can discover projects and pull environment values through a saved provider connection. Forge or command-based deployment configuration belongs to a specific target. Selecting such a connection does not authorize publishing; ask for the exact operation separately.

Diagnose a resource mismatch#

If the app reads different rows from Database, compare the configured host, database/schema and environment without printing the password. If mail does not arrive in the catcher, check which SMTP settings the app process actually loaded. A stale process can retain older environment values. Use Database and test mail to verify those paths directly.