Certainly! Here are additional examples for each use case of environment variables:
1. Configuration Settings
-
Email Server Configuration:
export SMTP_SERVER="smtp.example.com" export SMTP_PORT="587" -
Third-Party Service Credentials:
export STRIPE_SECRET_KEY="sk_test_4eC39HqLyjWDarjtT1zdp7dc"
2. Environment-Specific Variables
-
Testing Environment:
export NODE_ENV="testing" export DATABASE_URL="postgres://test_user:test_password@localhost:5432/test_db" -
Staging Environment:
export NODE_ENV="staging" export DATABASE_URL="postgres://staging_user:staging_password@localhost:5432/staging_db"
3. Path Management
-
Adding Python Scripts Directory to PATH:
export PATH="$PATH:$HOME/.local/bin" -
Setting Go Workspace:
export GOPATH="$HOME/go"
4. User Preferences
-
Customizing Terminal Appearance:
export TERM="xterm-256color" -
Setting Default Browser:
export BROWSER="firefox"
5. Security
-
Storing Database Password:
export DB_PASSWORD="my_secure_password" -
API Secret:
export API_SECRET="supersecretapikey"
6. Application Behavior
-
Setting Feature Flags:
export FEATURE_X_ENABLED="true" -
Configuring Cache Timeout:
export CACHE_TIMEOUT="3600" # in seconds
7. Shell Customization
-
Setting History Size:
export HISTSIZE="1000" -
Customizing Command Prompt Color:
export PS1="\[\e[32m\]\u@\h:\[\e[34m\]\w\[\e[0m\]\$ "
These additional examples further demonstrate the versatility of environment variables in managing configurations, enhancing security, and customizing user environments.
