Elysia Tools

Browse tools, examples, visual explainers, and topic guides from one clear workspace.

Top Categories

Hubs

Language
ZHDERUPTENFRES

Elysia Tools

Navigation

Data Formats

YAML configuration samples: types, nesting and document streams

Use YAML application, database, profile and Kubernetes examples to test scalar types, folded text and multi-document parsing.

Samples

Entries inside this sample collection

ConfigSimple

Simple Configuration File

Basic application configuration file

config
# Application Configuration
app:
  name: "MyWebApp"
  version: "1.0.0"
  environment: "development"

server:
  host: "localhost"
  port: 3000
  ssl: false

logging:
  level: "info"
  format: "text"
ConfigIntermediate

Database Configuration

Database connection configuration example

config
# Database Configuration
database:
  type: "postgresql"
  host: "localhost"
  port: 5432
  name: "myapp_db"

  credentials:
    username: "db_user"
    password: "secure_password"
    ssl: true

  pool:
    min: 2
    max: 10
    timeout: 30s

  connection:
    timeout: 10s
    retries: 3
    backoff: 1s
ConfigIntermediate

User Profile

YAML structure with user information

config
# User Profile
user:
  id: "USR12345"
  username: "johndoe"
  email: "john.doe@example.com"

  profile:
    first_name: "John"
    last_name: "Doe"
    age: 30
    bio: >
      Software developer passionate about
      creating amazing applications.
      Love working with modern technologies.

    interests:
      - "programming"
      - "photography"
      - "travel"

  preferences:
    theme: "dark"
    language: "en"
    timezone: "UTC-5"
    notifications:
      email: true
      push: false

  roles:
    - "user"
    - "developer"
ConfigIntermediate

Server Configuration

Web server configuration example

config
# Server Configuration
server:
  name: "Production Web Server"
  environment: "production"

  http:
    host: "0.0.0.0"
    port: 80
    timeout: 30s

  https:
    enabled: true
    port: 443
    certificate: "/etc/ssl/certs/server.crt"
    private_key: "/etc/ssl/private/server.key"

  middleware:
    - cors
    - rate_limit
    - compression
    - logging

  rate_limit:
    requests_per_minute: 100
    burst_size: 20

  cors:
    origins:
      - "https://example.com"
      - "https://app.example.com"
    methods:
      - GET
      - POST
      - PUT
      - DELETE
    headers:
      - Content-Type
      - Authorization
ConfigComplex

Docker Compose Configuration

Containerized application orchestration configuration

config
# Docker Compose Configuration
version: '3.8'

services:
  web:
    image: nginx:alpine
    container_name: web_server
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf:ro
      - ./ssl:/etc/ssl:ro
    depends_on:
      - app
    networks:
      - frontend

  app:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: web_app
    environment:
      NODE_ENV: "production"
      DATABASE_URL: "postgresql://user:password@db:5432/myapp"
      REDIS_URL: "redis://redis:6379"
    ports:
      - "3000:3000"
    volumes:
      - ./app:/usr/src/app
      - /usr/src/app/node_modules
    depends_on:
      - db
      - redis
    networks:
      - frontend
      - backend

  db:
    image: postgres:15
    container_name: postgres_db
    environment:
      POSTGRES_DB: "myapp"
      POSTGRES_USER: "user"
      POSTGRES_PASSWORD: "password"
    volumes:
      - postgres_data:/var/lib/postgresql/data
      - ./init.sql:/docker-entrypoint-initdb.d/init.sql:ro
    ports:
      - "5432:5432"
    networks:
      - backend

  redis:
    image: redis:7-alpine
    container_name: redis_cache
    command: redis-server --appendonly yes
    volumes:
      - redis_data:/data
    ports:
      - "6379:6379"
    networks:
      - backend

volumes:
  postgres_data:
  redis_data:

networks:
  frontend:
    driver: bridge
  backend:
    driver: bridge
ConfigIntermediate

Internationalization Messages

Multilingual messages configuration example

config
# Internationalization Messages
en:
  common:
    welcome: "Welcome to our application"
    login: "Login"
    logout: "Logout"
    register: "Register"

  navigation:
    home: "Home"
    about: "About"
    contact: "Contact"
    services: "Services"

  messages:
    success: "Operation completed successfully"
    error: "An error occurred"
    loading: "Loading..."
    no_data: "No data available"

  validation:
    required: "This field is required"
    email: "Please enter a valid email"
    min_length: "Minimum length is {count} characters"

zh:
  common:
    welcome: "欢迎使用我们的应用程序"
    login: "登录"
    logout: "登出"
    register: "注册"

  navigation:
    home: "首页"
    about: "关于"
    contact: "联系"
    services: "服务"

  messages:
    success: "操作成功完成"
    error: "发生错误"
    loading: "加载中..."
    no_data: "暂无数据"

  validation:
    required: "此字段为必填项"
    email: "请输入有效的邮箱地址"
    min_length: "最小长度为 {count} 个字符"

es:
  common:
    welcome: "Bienvenido a nuestra aplicación"
    login: "Iniciar sesión"
    logout: "Cerrar sesión"
    register: "Registrarse"

  navigation:
    home: "Inicio"
    about: "Acerca de"
    contact: "Contacto"
    services: "Servicios"

  messages:
    success: "Operación completada exitosamente"
    error: "Ocurrió un error"
    loading: "Cargando..."
    no_data: "No hay datos disponibles"

  validation:
    required: "Este campo es obligatorio"
    email: "Por favor ingrese un email válido"
    min_length: "La longitud mínima es {count} caracteres"
ConfigComplex

CI/CD Pipeline

Continuous integration configuration example

config
# CI/CD Pipeline Configuration
name: "CI/CD Pipeline"

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [18, 20]

    steps:
      - name: "Checkout code"
        uses: actions/checkout@v3

      - name: "Setup Node.js ${{ matrix.node-version }}"
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}
          cache: 'npm'

      - name: "Install dependencies"
        run: npm ci

      - name: "Run linting"
        run: npm run lint

      - name: "Run type checking"
        run: npm run type-check

      - name: "Run unit tests"
        run: npm run test:unit

      - name: "Run integration tests"
        run: npm run test:integration

  build:
    needs: test
    runs-on: ubuntu-latest

    steps:
      - name: "Checkout code"
        uses: actions/checkout@v3

      - name: "Setup Node.js"
        uses: actions/setup-node@v3
        with:
          node-version: '20'
          cache: 'npm'

      - name: "Install dependencies"
        run: npm ci

      - name: "Build application"
        run: npm run build

      - name: "Upload build artifacts"
        uses: actions/upload-artifact@v3
        with:
          name: build-files
          path: dist/

  deploy:
    needs: build
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'

    environment: production

    steps:
      - name: "Download build artifacts"
        uses: actions/download-artifact@v3
        with:
          name: build-files
          path: dist/

      - name: "Deploy to production"
        run: |
          echo "Deploying to production server..."
          # Add your deployment commands here

      - name: "Run smoke tests"
        run: npm run test:smoke
ConfigComplex

Kubernetes Deployment

Container orchestration deployment configuration

config
# Kubernetes Deployment Configuration
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-app
  namespace: production
  labels:
    app: web-app
    version: v1.0.0
spec:
  replicas: 3
  selector:
    matchLabels:
      app: web-app
  template:
    metadata:
      labels:
        app: web-app
        version: v1.0.0
    spec:
      containers:
      - name: web-app
        image: myregistry/web-app:1.0.0
        ports:
        - containerPort: 3000
          protocol: TCP

        env:
        - name: NODE_ENV
          value: "production"
        - name: DATABASE_URL
          valueFrom:
            secretKeyRef:
              name: app-secrets
              key: database-url
        - name: REDIS_URL
          valueFrom:
            configMapKeyRef:
              name: app-config
              key: redis-url

        resources:
          requests:
            memory: "256Mi"
            cpu: "250m"
          limits:
            memory: "512Mi"
            cpu: "500m"

        livenessProbe:
          httpGet:
            path: /health
            port: 3000
          initialDelaySeconds: 30
          periodSeconds: 10

        readinessProbe:
          httpGet:
            path: /ready
            port: 3000
          initialDelaySeconds: 5
          periodSeconds: 5

        volumeMounts:
        - name: config-volume
          mountPath: /app/config
          readOnly: true

      volumes:
      - name: config-volume
        configMap:
          name: app-config

      imagePullSecrets:
      - name: registry-secret

---
apiVersion: v1
kind: Service
metadata:
  name: web-app-service
  namespace: production
spec:
  selector:
    app: web-app
  ports:
  - protocol: TCP
    port: 80
    targetPort: 3000
  type: ClusterIP

---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-app-ingress
  namespace: production
  annotations:
    kubernetes.io/ingress.class: nginx
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  tls:
  - hosts:
    - app.example.com
    secretName: web-app-tls
  rules:
  - host: app.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: web-app-service
            port:
              number: 80

Tools

Tools frequently paired with this sample

Related

Related sample collections

Related

Related workflows

Tool usage guide

Sample-focused context for search and workflow understanding

Overview

Readable indentation can conceal a wrong parent key or an unexpected scalar type. Start with an application configuration, then test durations, folded biographies and multiple documents before handing YAML to a service.

Select a configuration by its failure mode

The examples are inline text cards: expand and copy the whole example, then paste into your own YAML editor or save it as UTF-8 .yaml. The collection does not provide independent downloads for these cards or apply a configuration to a server.

Select a configuration by its failure mode
Sample cardChoose it for
«Simple Configuration File»Nested mappings, port 3000 and ssl false
«Database Configuration»Integer retries and duration strings
«User Profile»Sequences, notification booleans and folded text
«Docker Compose Configuration»Services, quoted port mappings and volumes
«Internationalization Messages»Unicode text and interpolation placeholders
«Kubernetes Deployment»Three documents separated by ---

A YAML value is not yet an application setting

Use a YAML 1.2 core-compatible schema for the scalar checks below. Under that schema, 3000 is an integer, false is a boolean and 10s is text. A database client may interpret 10s as a duration, but that interpretation comes after YAML parsing. Quoted versions and port mappings should remain strings.

Indentation determines the parent mapping or sequence; tabs are unsuitable for indentation. Compare the parsed structure after an edit instead of judging alignment only by eye. For document streams, use a multi-document loading function and check every document rather than reading just the first.

Which tools to test with these samples

Use these files with a YAML Formatter, a YAML-JSON Converter, a YAML File Merger for combining configs, and a TOML-YAML Converter for cross-format migration. The configurations with failure modes expose how a tool reports indentation and syntax errors.

Every file in this set is YAML. The samples cover valid configurations, nested structures and failure cases — the same shapes a formatter or converter meets when a real config file breaks.

How it works

  1. 1Choose one code card and copy all of it, preserving spaces and document separators.
  2. 2Load it in an external YAML parser with an explicit schema; inspect types as well as displayed values.
  3. 3Validate the resulting object against the target application separately, then check that serialization retains intended strings and structure.

Edge cases & common failures

  • Parser schemas differ

    Older YAML 1.1 resolvers may interpret words such as on differently. «CI/CD Pipeline» uses on as a key; choose the schema expected by the consuming system and verify the loaded key.

  • Infrastructure dependencies are external

    Compose paths, certificates, Kubernetes secrets and images are references. This collection does not bundle them; syntactically correct YAML alone cannot make the deployment run.

Examples

1. Separate a duration from an integer

How to use

Load «Database Configuration» with a core schema. Inspect database.connection.timeout and database.connection.retries, then compare database.credentials.ssl.

Outcome

timeout is the string 10s, retries is integer 3 and ssl is boolean true. The parser has not converted 10s into milliseconds; passing it to a numeric-only API requires a deliberate conversion.

2. Check folding without losing words

How to use

Load «User Profile» and inspect user.profile.bio, interests and user.preferences.notifications.push.

Outcome

The three biography source lines fold into one text paragraph with a final line break. interests contains three entries and push is false. The > indicator folds normal line breaks; it does not create an array of lines or enable a notification.

3. Read every Kubernetes document

How to use

Copy «Kubernetes Deployment» and use a multi-document loader. List kind from each document, then inspect the first document’s spec.replicas and the second document’s spec.ports[0].targetPort.

Outcome

The three kinds are Deployment, Service and Ingress, in that order; replicas is 3 and targetPort is 3000. Separators create distinct documents, so treating this as one mapping loses the service or ingress configuration.

FAQ

Will comments survive a load-and-dump conversion?

A basic object loader often drops comments and formatting. Use a document-preserving editor if comments matter to the handoff.

Is {count} already substituted in translation messages?

No. «Internationalization Messages» stores quoted message text containing {count}. Your translation system performs interpolation later; preserve the placeholder during conversion.

Hub

Tabular Data Cleanup, Shaping, and Normalization

Take messy tabular data to analysis-ready — merge source tables into one, strip the byte-order marks that break column matching, keep only the columns you need, fix spellings and formats, handle outliers by policy instead of panic, scale or standardize the numbers, and finish with range limits and a crosstab summary.

Hub

Geospatial Coordinate Conversion and Map Data Workflow

Normalize coordinate formats, verify locations, calculate distance and bearing, then convert GeoJSON, KML, OSM, and GPX data for downstream mapping work.

Hub

Infer JSON Schema from Samples and Spreadsheets

Derive a reviewable JSON Schema draft from representative JSON samples or XLSX rows, then inspect types, requiredness, nulls, and outliers before treating it as a contract.

Hub

Audio Metadata, Tags, Chapters, and Album Art

Prepare music or podcast files by checking tags, managing artwork, adding chapters, and cleaning delivery metadata.

Home
Tools3212
Samples593
Visualizations471
Viewers103
Hubs239
Tags333
Images, Audio & Video657

Image, audio, and video processing, conversion, and optimization tools

Math, Date & Finance647

Calculators, numerics, date logic, statistics, and finance tools

Design & Color298

Color, layout, graphics, visual styling, and design helper tools

Text & Writing209

Writing, cleanup, formatting, extraction, and text analysis tools

Developer & Web193

Developer utilities, networking, web debugging, and automation helpers

Conversion & Encoding175

Format, file, archive, unit, and encoding conversion tools

Lead Generation Quiz Launch and Contact Handoff
Memorial Drafts: Family Review and Print Handoff
Private Habit Records: Backup, Restore and Sharing Review
Article to X and LinkedIn Drafts: Fact Review and Handoff
Markdown Interactive Deck Review and Offline Handoff

© 2026 Elysia Tools. All rights reserved.

DocsPricingAboutTerms of ServicePrivacy PolicyCookiesContact

Format Conversion

HCL-YAML Converter

Convert between HashiCorp Configuration Language (HCL) and YAML formats for Terraform configurations

Format Conversion

TOML-YAML Converter

Convert between TOML and YAML formats with support for complex data structures and configuration files

Data Processing

YAML File Merger

Merge multiple YAML files with various strategies (deep merge, overwrite, combine arrays, etc.)

Format Conversion

YAML Formatter

Format and beautify YAML. Note: comments are lost (js-yaml limitation)

Format Conversion

YAML-JSON Converter

Convert between YAML and JSON formats

Format Conversion

TOML / INI / HCL / .env / Nix / dotenv ⇄ Kubernetes ConfigMap & Secret Config Format Bridge

Convert configuration files between dotenv .env, TOML, INI, Java .properties, YAML, JSON, HCL (Terraform/Vagrant native syntax) and Nix attribute sets, and emit Kubernetes ConfigMap or Secret manifests. Template placeholders (${VAR}, {{var}}, envsubst) are preserved verbatim, type inference provenance (string/int/float/bool/list) is tracked, HCL block labels fold into nested keys, and a round-trip diff calls out non-equivalent settings — dropped keys, re-typed values and rewrites — instead of coercing them silently.

Development

Config File Semantic Diff

Compare JSON, YAML, TOML, and dotenv configurations by key path while ignoring ordering and formatting noise.

Development

Environment Config Diff Visualizer

Compare dev, staging, and production configuration bundles across JSON, YAML, TOML, or ENV formats and highlight drift, missing keys, and cleanup suggestions

Development

YAML Viewer Samples

Sample YAML files (app config, docker-compose, k8s) for the in-browser YAML Viewer

Observability

Distributed Tracing Samples

Comprehensive distributed tracing examples using Jaeger, OpenTelemetry, and other modern observability tools for microservices architecture

Monitoring

Grafana Advanced Application Samples

Comprehensive Grafana samples covering advanced dashboard design, alerting configurations, data source integrations, and plugin development

Container Orchestration

Kubernetes YAML Samples

Complete Kubernetes YAML manifests for Deployment, Service, ConfigMap, Secret, Ingress and other essential resources

API Documentation

OpenAPI/Swagger Samples

Comprehensive API documentation examples using OpenAPI 3.0 and Swagger specifications for RESTful services

Observability & Monitoring

Prometheus Monitoring

Comprehensive Prometheus monitoring and alerting system examples including custom metrics exporters, alert rule configuration, PromQL queries, and Grafana dashboard integration