User directory for configs is set by RADICAL_CONFIG_USER_DIR env variable here (by default $HOME dir is used) and has hierarchy which is similar to what method get_radical_base (RADICAL_BASE -> get_base) produces here.
Proposal to have one approach (a single method) for a base directory to keep temporary files (cache), configs, etc.
Base directory
- client: local files and user configs
- Follow XDG Base Directory specification
- user-specific configs, default to
$HOME/.config, e.g., $HOME/.config/radical/pilot/resource_ornl.json or $XDG_CONFIG_HOME/radical/pilot/resource_ornl.json ($XDG_CONFIG_HOME/resource_ornl.json?)
- user-specific data, default to
$HOME/.local, e.g., $HOME/.local/radical/saga/adaptors
- pilot (remote)
- currently:
RADICAL_BASE contains resource sandbox path (…/radical.pilot.sandbox)
User directory for configs is set by
RADICAL_CONFIG_USER_DIRenv variable here (by default$HOMEdir is used) and has hierarchy which is similar to what methodget_radical_base(RADICAL_BASE->get_base) produces here.Proposal to have one approach (a single method) for a base directory to keep temporary files (cache), configs, etc.
Base directory
$HOME/.config, e.g.,$HOME/.config/radical/pilot/resource_ornl.jsonor$XDG_CONFIG_HOME/radical/pilot/resource_ornl.json($XDG_CONFIG_HOME/resource_ornl.json?)$HOME/.local, e.g.,$HOME/.local/radical/saga/adaptorsRADICAL_BASEcontains resource sandbox path (…/radical.pilot.sandbox)