User Tools

Site Tools


Using the command line

Available params

  • Many params are available on the command line. Most of them are used by developers for tests.
  • --version, -version, -v
    • Show the version number and some technical details of the application.
  • --help, -help, -h
    • Show the command line help
  • --config=/path/to/config.ini, --config=../../relative/path/config.ini
    • Define the configuration file to use. In the case this file is specified, with a debug build, all resources (pixmaps, SQLite db, text files…) of the application will be searched in the same path as the file.
  • --wine
    • Ensure wine compatibility (obsolet)
  • --clear-user-databases
    • Erase all existing user databases and recreate them. BEWARE: there will be NO backup of the existing if you are using MySQL.
  • --create-virtuals
    • Create virtual data in order to ease tests (patients, users, calendars and agenda events). More details here.
  • --reset-users-preferences
    • Force EHR to recreate all user preferences at each connection/reconnection (not yet available).
  • --user-clear-log
    • Connect with this clear login.
    • Since version 0.7.2
  • --user-clear-password
    • Connect with this clear password
    • Since version 0.7.2
  • --dont-check-form-update
    • Do not check for form updates at startup
    • Since version 0.8.2
  • --always-update-forms
    • Check for form updates at startup and install them without asking for confirmation
  • --no-check-update
    • Do not check if an update for the app is available by downloading the update text on the project's website update url

Other way to pass params to the application

  • The file pathtoconfig.ini is always scanned. If such a file exists next to the binary, it will be used.
  • Command line params will be overriden.
  • You can define the path the configuration file using relative or absolute path (equals to --config=xxx).
en/manuals/freemedforms/info/commandline.txt · Last modified: 2017/04/24 07:09 by Jérôme Pinguet