Build, run, and deploy profiles

Profile types

Profiles are reusable operating recipes. A build profile describes how to compile something, a run profile describes how to launch it, and a deploy profile describes how to publish it to an environment.

Pick the profile that matches the question you are answering: local development, shared preview, package validation, or production-style deployment.

• Use development profiles for fast local iteration.
• Use preview profiles when sharing a running build through a stable URL.
• Use deployment profiles when building packages or publishing to a target host.

Profile checklist

A strong profile is specific enough to run safely and simple enough to remember. Before relying on one, confirm that it captures the operational details users otherwise have to repeat.

Configuration

Configuration should be explicit and environment-specific.

• Document required ports, base URLs, credentials, and data roots.
• Keep machine-specific secrets out of public docs and committed config.
• Fail visibly when required configuration is missing.

Validation

A profile is only correct if the intended route works after launch. For website work, that usually means build success, process start, HTTP response, page title or heading, and no obvious server log errors.

Ask Buffaly to report which profile it used, which URL it verified, and which log or command output proves the run matched the intended environment.

• Build before running a profile.
• Open the expected URL and verify the page or API route.
• Check logs when the process starts but the browser path fails.

Good requests and common mistakes