Child pages
  • The Opmantek Installer

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: note re init scripts vs no local mongodb

...

Info
titleOpmantek Installer

All Opmantek products make use of an interactive installer program that greatly simplifies both initial installation AND upgrading an existing installation.

 


This  document explains the most essential installer features.

...

The combination of --noexec and --keep provides the equivalent of unpacking the tar files provided with earlier releases.

 


You can also pass options to the interactive installer component, but these must follow after a "--" delimiting argument:

...

  • By default the installer is interactive and will prompt you for decisions and confirmations; If you want to run it in non-interactive batch mode, use the -y option.
    In this case all dialogs and prompts are automatically answered with the default answer (usually 'y').
  • Please note that in non-interactive mode the installer will abort upgrades if critical incompatibilities (e.g. license type) are detected; the option to overrule the installer in such situations is only present when the installer is running interactively.
  • Certain installer choices can be preset for non-interactive mode:
    1. Setting the environment variable NO_LOCAL_MONGODB to a non-empty value instructs the installer to not install a local MongoDB server even if none is present.
      Please note that you will have to manually adjust the Opmantek daemon init scripts or systemd unit files after installation, as these express the dependency on a local  MongoDB installation.
  • If you want to install the product into a non-standard directory, you can pass the argument -t <targetdir> to the installer component.
    Please note that you will have to adjust a number of configuration files in this case.
  • It is possible to generate more detailed diagnostic output in the installer log file, using the -d option.

...

  • What's this warning about "incorrect checksum detected"?
    This can happen very infrequently,  if you are installing an older Opmantek application on top of newer ones, or if you've made extensive changes to your system's Opmantek files.
    We strive hard to line up our releases properly so that everything meshes cleanly, but every now and then there are minor changes to files that older installer versions aren't quite aware of.

    In general this warning dialog is safe to answer with 'yes' and the installer will leave your system in a consistent working state (by replacing the unrecognizable/mismatching file with a known good version from the shipped product).

 


Please feel free to submit your comment here or email us with your questions!

...