Deploying code

Edge projects use a small manifest file at the repository root—typically 8080.yaml (sometimes 8080.yml)—that tells the platform how to run your application. The CLI (8080 init, 8080 deploy) reads this file when building and deploying.

Runtime

Deployments today use a Python runtime: you provide an ASGI application (for example built with the e80 SDK and eighty80_app()). TypeScript and JavaScript application runtimes are coming soon; this page documents the current Python-oriented manifest.

Example 8080.yaml

entrypoint: handlers.main:app
organization_slug: your-organization
project: examples
project_slug: examples
cpu_mhz: 500
gpu_count: 0
memory_size_mb: 1024

Field reference

Field	Type	Description
entrypoint	string	Python import path to the ASGI app, in the form module.path:variable. The module path uses dots for packages (e.g., handlers.main → handlers/main.py or package layout). The variable is the app instance (e.g., FastAPI / Starlette / SDK app). Example: handlers.main:app loads app from handlers.main.
organization_slug	string	Organization identifier in 8080 (matches your team/org in the dashboard and CLI context).
project	string	Human-readable project name (display and grouping).
project_slug	string	Stable project slug used in URLs, routing, and hosting (e.g., {project_slug}.hosted.8080.io patterns where applicable).
cpu_mhz	number	CPU allocation for the deployment, in megahertz (e.g., 500).
gpu_count	integer	Number of GPUs attached to each instance. Use 0 for CPU-only workloads.
memory_size_mb	integer	RAM limit per instance in megabytes (e.g., 1024 for 1 GB).

Creating or editing the file

1. Run 8080 init in an empty directory to scaffold a project, or add 8080.yaml yourself next to your Python package and handler code.
2. Set entrypoint to the module and app object that exposes your HTTP API (must match how you run locally with 8080 dev).
3. Align organization_slug, project, and project_slug with your org and project in the 8080 dashboard.
4. Tune cpu_mhz, gpu_count, and memory_size_mb to your latency and throughput needs; invalid or unsupported combinations may be rejected at deploy time.

For a full walkthrough of a minimal handler and local run, see Custom endpoints.