Serverless Runner

Terminal-first devtools toolkit for checking, validating, generating, formatting, linting, and managing code and configuration — all from the command line.

Why Serverless Runner?

• Works entirely offline — your data never leaves your machine
• Complete devtools workflow: check → validate → generate → format → lint → fix → report
• Template and diff support for code generation and comparison
• Export to JSON, CSV, or plain text anytime
• Automatic history and activity logging with timestamps

Getting Started

# See all available commands
serverless-runner help

# Check current health status
serverless-runner status

# View summary statistics
serverless-runner stats

# Show recent activity
serverless-runner recent

Commands

Each devtools command works in two modes:

• With arguments: saves the input with a timestamp to <command>.log and logs to history
• Without arguments: displays the 20 most recent entries for that command

Data Storage

All data is stored locally at ~/.local/share/serverless-runner/:

• check.log, validate.log, generate.log, etc. — one log file per command
• history.log — unified activity log with timestamps
• export.json, export.csv, export.txt — generated export files

Data format: each entry is stored as YYYY-MM-DD HH:MM|<value> (pipe-delimited).

Set the SERVERLESS_RUNNER_DIR environment variable to change the data directory.

Requirements

• Bash 4+ (uses set -euo pipefail)
• Standard UNIX utilities: wc, du, grep, tail, sed, date, cat, basename
• No external dependencies or network access required

When to Use

1. Checking and validating configs — run check and validate on config files, YAML, or JSON before deploying
2. Generating boilerplate — use generate and template to scaffold new projects or components
3. Linting and auto-fixing code — chain lint → fix to catch and resolve style issues automatically
4. Comparing versions — use diff and preview to review changes before committing
5. Exporting devtools reports — generate JSON, CSV, or TXT snapshots of your activity for auditing or sharing

Examples

# Check a configuration file
serverless-runner check "nginx.conf syntax valid"

# Validate and lint
serverless-runner validate "docker-compose.yml schema check"
serverless-runner lint "src/main.py flake8 style"

# Generate from template and preview
serverless-runner generate "new-service from microservice-template"
serverless-runner template "microservice: port=8080 name=auth-svc"
serverless-runner preview "auth-svc deployment manifest"

# Diff two versions, then auto-fix
serverless-runner diff "v1.2.0 vs v1.3.0 config changes"
serverless-runner fix "auto-fix lint warnings in src/"

# Export everything as JSON, then search
serverless-runner export json
serverless-runner search "nginx"

# Check overall health
serverless-runner status
serverless-runner stats

Output

All commands return human-readable output to stdout. Redirect to a file for scripting:

serverless-runner stats > report.txt
serverless-runner export csv

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com