Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Since Commit d6abb0 we are using global .env files. They are located in /etc/nmsprime/env/*.env. Each module that requires separate env settings, deploy there own *.env file. Deployment is done with Install API – config files. These files are automated filled with random passwords during install, for example: Install/after_install.sh

 

1. Descriptions

SectionValueUsageNote
NMS PrimeAPP_ENV  
 APP_DEBUG  
 APP_KEY  
 APP_LOG  
    
DatabaseDB_HOST  
    

 

2. Examples

A) global.env

.env
# this is the global configuration file

APP_ENV=local
APP_DEBUG=false

# generate using "php artisan key:generate"
APP_KEY=base64:l064arTFEris8J... # key auto generated during install

# overwrite logging behavior in config/app.php ? read comments there to learn possible values
APP_LOG=single
APP_LOG_LEVEL=info

DB_HOST=localhost
DB_DATABASE=nmsprime
DB_USERNAME=nmsprime
DB_PASSWORD=Tie3azw6oobf

CACHE_DRIVER=file
SESSION_DRIVER=file
QUEUE_DRIVER=database

# BaseURL used in console commands
APP_CONSOLE_BASEURL='https://localhost:8080/nmsprime'

# HTTPS Port settings
HTTPS_ADMIN_PORT=8080

  • No labels