
Security News
Package Maintainers Call for Improvements to GitHub’s New npm Security Plan
Maintainers back GitHub’s npm security overhaul but raise concerns about CI/CD workflows, enterprise support, and token management.
@buildappolis/env-manager
Advanced tools
Enterprise-grade environment variable management system with encryption, snapshots, and validation
BuildAppolis Env-Manager is a powerful, secure environment variable management system designed for modern applications. It provides encrypted storage, version control, snapshots, and validation for your environment configurations.
This software is licensed under the BuildAppolis License. Key points:
See LICENSE for full terms.
# Install env-manager globally
npm install -g @buildappolis/env-manager
# Now you can use env-manager command directly!
env-manager init
# This will:
# 1. Create env.config.ts template
# 2. Set up your password securely
# 3. Configure .env settings
# Start the service
env-manager start
# Open the UI
env-manager open
# Run without installing
npx @buildappolis/env-manager init
Once installed globally, you can use these commands:
# Initialize project with env-manager
env-manager init
# Set or change master password
env-manager setup-password
# Recover password using recovery phrase
env-manager recover-password
# Start the service
env-manager start
env-manager start --project /path/to/project # Start specific project
# List all registered projects
env-manager projects
# Check service status
env-manager status
# Open UI in browser
env-manager open
# Show help
env-manager --help
Access the UI at http://localhost:3001
To completely remove env-manager and all its data:
# 1. Uninstall the package
npm uninstall -g @buildappolis/env-manager
# or
pnpm uninstall -g @buildappolis/env-manager
# 2. Remove all configuration and data files
rm -rf ~/.env-manager/ # Global config and passwords
rm -rf ~/.env-manager-registry/ # Project registry
rm -rf ~/.env-manager-data/ # Database files
To reset env-manager to factory defaults without uninstalling:
# Remove all configuration files but keep the package
rm -rf ~/.env-manager/
rm -rf ~/.env-manager-registry/
rm -rf ~/.env-manager-data/
# You'll need to set up password again
env-manager setup-password
To remove env-manager from a specific project:
# In your project directory
rm -f env.config.ts # Remove config file
rm -f env.config.js # Remove compiled config (if exists)
rm -rf .env-manager/ # Remove project-specific data
rm -rf .env-manager-logs/ # Remove log files
# If installed as dependency
npm uninstall @buildappolis/env-manager
# or
pnpm uninstall @buildappolis/env-manager
Env-Manager stores data in the following locations:
Data Type | Location | Purpose |
---|---|---|
Global Password | ~/.env-manager/credentials.json | Master password and recovery phrase |
Project Registry | ~/.env-manager-registry/registry.json | List of all registered projects |
Project Databases | ~/.env-manager-data/ | SQLite databases for each project |
Project Logs | <project>/.env-manager-logs/ | Runtime logs for each project |
Project Config | <project>/env.config.ts | Project-specific configuration |
If you're having issues:
pkill -f "env-manager"
lsof -i :3001 | grep LISTEN | awk '{print $2}' | xargs kill -9
rm -rf ~/.env-manager-data/<project-name>.db
Env-Manager works seamlessly with all major frameworks. See our comprehensive Framework Integration Guide for detailed examples with:
Quick example with Next.js:
# Initialize in your Next.js project
env-manager init
# Start both env-manager and Next.js dev server
npm run dev # Add "env-manager start &" to your dev script
// env.config.ts in your project root
export default {
projectName: 'My App',
envManager: {
enabled: true,
url: 'http://localhost:3001',
apiKey: process.env.ENV_MANAGER_API_KEY
},
requirements: {
database: {
required: true,
variables: [
{ name: 'DATABASE_URL', required: true, sensitive: true },
{ name: 'DB_POOL_SIZE', required: false, default: '10' }
]
}
}
}
FROM node:20-alpine
WORKDIR /app
COPY . .
RUN npm install
RUN npm run build
EXPOSE 3001
CMD ["npm", "start"]
# Build and run
docker build -t buildappolis/env-manager .
docker run -p 3001:3001 -v $(pwd)/data:/app/data buildappolis/env-manager
# Server Configuration
PORT=3001
HOST=0.0.0.0
# Security
ENV_MANAGER_PASSWORD=your-secure-password
ENCRYPTION_KEY=your-32-char-encryption-key
# Database
DATABASE_PATH=./data/env-manager.db
# Features
ENABLE_SNAPSHOTS=true
ENABLE_EXPORT=true
ENABLE_API=true
Create an env.config.ts
in your project root:
import type { EnvConfig } from '@buildappolis/env-manager'
export default {
projectName: 'Your Project',
projectVersion: '1.0.0',
requirements: {
core: {
required: true,
variables: [
{
name: 'NODE_ENV',
required: true,
validation: /^(development|staging|production)$/,
description: 'Application environment'
}
]
}
}
} satisfies EnvConfig
For commercial use, you have two options:
Use our managed cloud service at www.buildappolis.com
Purchase a commercial license for self-hosting:
Contact: license@buildappolis.com
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
By contributing, you agree that your contributions will be licensed under the same license.
Full documentation is available at docs.buildappolis.com/env-manager
Built with ❤️ by BuildAppolis
[1.4.12] - 2025-08-19
env-manager port set
commandFAQs
Enterprise-grade environment variable management system with encryption, snapshots, and validation
We found that @buildappolis/env-manager demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maintainers back GitHub’s npm security overhaul but raise concerns about CI/CD workflows, enterprise support, and token management.
Product
Socket Firewall is a free tool that blocks malicious packages at install time, giving developers proactive protection against rising supply chain attacks.
Research
Socket uncovers malicious Rust crates impersonating fast_log to steal Solana and Ethereum wallet keys from source code.