smithery/valec3

backend-deployment-configuration

Environment config, .env management.

Installation

$ npx skills add smithery/valec3 --skill backend-deployment-configuration

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/valec3 · top by installs.

npx skills add smithery/valec3

Browse all from smithery/valec3

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,123 B
  • docs SUMMARY.md 76 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Backend Deployment Configuration

When to use this skill

  • Environment setup
  • Configuration management
  • Deployment
  • Security

Workflow

  • Use .env for config
  • Never commit .env
  • Separate dev/staging/prod
  • Validate required vars
  • Document configuration

Instructions

.env File

# .env
CI_ENVIRONMENT = production

database.default.hostname = localhost
database.default.database = myapp
database.default.username = dbuser
database.default.password = secret
database.default.DBDriver = MySQLi

JWT_SECRET = your-secret-key
API_KEY = external-api-key

Usage

<?php

$dbHost = env('database.default.hostname');
$jwtSecret = env('JWT_SECRET');

Required Vars Check

<?php

$required = ['JWT_SECRET', 'database.default.password'];
foreach ($required as $key) {
    if (!env($key)) {
        throw new \RuntimeException("Missing env var: {$key}");
    }
}

Resources

  • Use .env for all config
  • Different .env per environment
  • Never commit secrets