HOP server runtime command files == Description == These server parameters control the RC file loaded when HOP execution starts. Examples of such file can be found in the tutorial section. ~~ The RC file ,( "tutorial" "07-hoprc.wiki") shows how this file can be used to customize Hop. == Synopsis == (hop-rc-directory) (hop-rc-directory-set! arg) (hop-rc-file) (hop-rc-file-set! arg) (hop-script-file) (hop-script-file-set! arg) == Server Definitions == === ++hop-rc-directory++ === hop-rc-directory hop-rc-directory-set! ^ access ^ type ^ current value ^ short description ^ | r/w | string | ++,(hop-rc-directory)++ | The path of rc files. | The path of the directory containing the ++(hop-rc-file)++ file. === ++hop-rc-file++ === hop-rc-file hop-rc-file-set! ^ access ^ type ^ current value ^ short description ^ | r/w | string | ++,(hop-rc-file)++ | The rc file. | The RC file is loaded *before* the ++(hop-script-file)++, just *after* the command line options have been parsed. === ++hop-script-file++ === hop-script-file hop-script-file-set! ^ access ^ type ^ current value ^ short description ^ | r/w | string | ++,(hop-script-file)++ | The script file. | The script file is loaded *after* the ++(hop-rc-file)++, just *before* the HOP main loop is entered. === ++hop-user++ === hop-user hop-user-set! ^ access ^ type ^ current value ^ short description ^ | r/w | string | ++,(hop-user)++ | The fallback user. | If started as root, HOP will drop root privileges and run as this ++(hop-user)++ instead. Otherwise, HOP will run as the user it was started by. If set to the symbol (not the string) ++root++, HOP will not drop root privileges at all (not recommended).