OnDemand’s configuration is stored in the environment, which can be modified using a hierarchy of config files. Configuration files are rooted in
/etc/ood. Assets that should be publicly available (such as a favicon or logo image) are placed under
- If exists, this file is sourced instead of the default at
/opt/ood/nginx_stage/sbin/nginx_stagescript when running as root, prior to launching the PUN.
- You should source
/opt/ood/nginx_stage/etc/profilein your custom
/etc/ood/profileif you add one to load the correct software collections.
- YAML file to override default configuration for the PUN. You can set environment variables via key-value pairs in the mapping
pun_custom_env. You can specify a list of environment variables set in
/etc/ood/profileto pass through to the PUN by defining the sequence
- An example of both of these uses may be found in nginx_stage_example.yml. Variables set here are set for all OnDemand applications.
- Used to provide application specific config
envfiles do not override values set by prior methods.
- Modify Rails application behavior using Ruby code. Since this is application code environment variables can be set, removed.
- This method is specific to Ruby on Rails applications: Activejobs, Dashboard, File Editor, and Job Composer. You can add multiple initializer files in this directory and they will be loaded in alphabetical order