GitHub - Thanos2002/Oneconfig: Set up any dev environment with one command.

oneconfig generate   →   scans your project, builds a config
oneconfig up         →   installs everything, starts all services

That's it. No Dockerfiles to write. No READMEs to follow. No "works on my machine."

💡 The Problem

Every project has the same onboarding pain:

"Clone the repo, install Node 20, make sure you have Postgres running, oh and you need Redis too, then copy .env.example, run the migrations, seed the database, then…"

OneConfig eliminates all of that. It deep-scans your repository, infers your entire stack—languages, runtimes, package managers, databases—and generates a single oneconfig.yml that describes your full environment. Then it provisions everything automatically, in the right order, with health checks.

New developer? One command. Done.

✨ Why OneConfig?

🚀 Quick Start

Prerequisites

• Go 1.21+ installed on your machine

1. Install

go install github.com/Thanos2002/Oneconfig@latest

Note: go install uses the last part of the module path for the binary name, so this will install as Oneconfig (with a capital O). On case-sensitive systems (Linux/macOS), you may need to alias it or rename the binary to oneconfig to follow the docs.

Note: Ensure $GOPATH/bin (or $HOME/go/bin) is in your system PATH so the command is available globally.

2. Generate

Navigate to any project and let OneConfig figure out your stack:

cd your-project/
oneconfig generate

This will scan your codebase and create a tailored oneconfig.yml—detecting your runtimes, package managers, frameworks, and databases automatically.

3. Launch

OneConfig will install runtimes, resolve dependencies, start databases, run migrations, boot your app, and verify health checks—all in the correct order.

✔ Validated oneconfig.yml
✔ Installed Node.js 20.x
✔ Ran npm install
✔ Started postgres (healthy on :5432)
✔ Ran migrations
✔ Started api (healthy on :3000)

🚀 Environment ready — http://localhost:3000

🧠 Universal Detection Engine

When you run oneconfig generate, the engine recursively traverses your project (including monorepos) and automatically identifies:

Extensible by design: Adding support for a new technology is as simple as creating a single detector_*.go file.

⚙️ The oneconfig up Lifecycle

Under the hood, the orchestrator executes a deterministic pipeline:

  oneconfig.yml
       │
       ▼
┌──────────────┐
│   Validate   │  ← Schema & dependency checks
└──────┬───────┘
       ▼
┌──────────────┐
│   Runtimes   │  ← Install Node.js, Python, Ruby, etc.
└──────┬───────┘
       ▼
┌──────────────┐
│ Dependencies │  ← npm install, poetry install, cargo build…
└──────┬───────┘
       ▼
┌──────────────┐
│  Env Vars    │  ← Inject variables into .env
└──────┬───────┘
       ▼
┌──────────────┐
│  Services    │  ← Boot in dependency order (DB → API → Workers)
└──────┬───────┘
       ▼
┌──────────────┐
│Health Checks │  ← TCP / HTTP probes per service
└──────┬───────┘
       ▼
┌──────────────┐
│  Post-Start  │  ← Migrations, seeds, notifications
└──────────────┘

📄 Example Configuration

Here's what oneconfig generate might produce for a typical full-stack Node.js + Postgres application:

project_name: my-app

runtimes:
  - name: node
    version: "20.x"

package_managers:
  - type: npm
    path: .

env_vars:
  NODE_ENV: development
  DATABASE_URL: postgres://localhost:5432/myapp

services:
  - name: postgres
    type: docker
    start_command: docker run -p 5432:5432 postgres:15
    port: 5432
    health_check:
      type: tcp
      target: ":5432"
      timeout: 30s

  - name: api
    start_command: npm run dev
    port: 3000
    depends_on: [postgres]
    health_check:
      type: http
      target: http://localhost:3000/health

setup_steps:
  - name: migrate
    command: npm run db:migrate
    depends_on: [postgres]

post_start_commands:
  - echo "🚀 Application ready at http://localhost:3000"

⌨️ CLI Reference

🤝 Contributing

We welcome contributions! OneConfig's detection engine is designed to be highly extensible—adding support for a new framework or tool typically requires just one new file.

See the Contributing Guide for full details on how to get started.