Software: Apache/2.4.41 (Ubuntu). PHP/8.0.30 

uname -a: Linux apirnd 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64 

uid=33(www-data) gid=33(www-data) groups=33(www-data) 

Safe-mode: OFF (not secure)

/var/www/html/proxy_server/node_modules/nodemon/doc/cli/   drwxr-xr-x
Free 13.13 GB of 57.97 GB (22.65%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Self remove    Logout    

Viewing file:     config.txt (1.13 KB)      -rw-r--r--

  Typically the options to control nodemon are passed in via the CLI and are
  listed under: nodemon --help options

  nodemon can also be configured via a local and global config file:

  * $HOME/nodemon.json
  * $PWD/nodemon.json OR --config <file>
  * nodemonConfig in package.json

  All config options in the .json file map 1-to-1 with the CLI options, so a
  config could read as:

    {
      "ext": "*.pde",
      "verbose": true,
      "exec": "processing --sketch=game --run"
    }

  There are a limited number of variables available in the config (since you
  could use backticks on the CLI to use a variable, backticks won't work in
  the .json config).

  * {{pwd}} - the current directory
  * {{filename}} - the filename you pass to nodemon

  For example:

    {
      "ext": "*.pde",
      "verbose": true,
      "exec": "processing --sketch={{pwd}} --run"
    }

  The global config file is useful for setting up default executables
  instead of repeating the same option in each of your local configs:

    {
      "verbose": true,
      "execMap": {
        "rb": "ruby",
        "pde": "processing --sketch={{pwd}} --run"
      }
    }