TeleFork.dev Documentation
Welcome to the TeleFork developer platform. TeleFork allows engineering teams to deploy ephemeral sandboxes automatically for every pull request, mirroring the production environment.
Quickstart Guide
You can configure your workspace in seconds using the TeleFork CLI. Open your terminal and execute:
The `init` script scans your root folder for Terraform, OpenTofu, or Helm setups, and automatically outputs a `.telefork/telefork.yaml` file.
Authentication
API access is structured around bearer tokens. Workspace keys are managed in the security admin console.
To supply authentication tokens in raw HTTP clients:
Infrastructure-as-Code Integration
TeleFork parses native IaC files. The engine interprets dependency schemas, isolating cloud variables securely. Here is a typical Terraform resource mapping setup:
During execution, the parsing engine detects `aws_db_instance` and substitutes it with an ephemeral Postgres Docker setup to reduce cloud charges.
Database Seeding
To specify database seeding subsets, edit your `telefork.yaml` configuration:
Compliance & Compliance configurations
Ensure strict data isolation. Compliance regulations require zero production user logs in dev environments. TeleFork's built-in tokenizers automatically swap user strings with randomized hashes before writing data images.
Webhooks
Register hooks to retrieve real-time workspace updates. When a sandbox finishes provisioning, TeleFork posts metadata to your specified webhook URL:
SDKs & Library Clients
Official client SDKs are available for Node.js, Go, and Python to manage sandbox instances programmatically:
- Node.js:
npm install @telefork/sdk - Go:
go get github.com/telefork/sdk-go - Python:
pip install telefork-sdk