AirInvServer(1)

πŸ“¦
version 1.00.15 Β· 3 versions
, in fedora 44

✨ AirInvServer(1) ✨

okay bestie, this is the page for AirInvServer from the General Commands Manual πŸŽ€ I read the whole thing so you don't have to πŸ’…

✨ NAME ✨

AirInvServer - a ZeroMQ-based server binary that exposes the AirInv library as a service πŸ¦‹

✨ SYNOPSIS ✨

AirInvServer [--prefix] [-v|--version] [-h|--help] [-b|--builtin]
[-f|--for_schedule] [-i|--inventory <path-to-inventory-input-file>]
[-s|--schedule <path-to-schedule-input-file>] [-o|--ond <path-to-ond-input-file>]
[-y|--yield <path-to-yield-input-file>] [-t|--protocol <server network protocol>]
[-a|--address <server host address>] [-p|--port <server host port>]
[-l|--log <path-to-output-log-file>]

✨ DESCRIPTION ✨

So AirInvServer is a little program that wraps the AirInv library and serves it up as a ZeroMQ-based server 🌸 The server listens for requests and answers with JSON-formatted messages. Usually a Django-based Web app is the one talking to it, so the end user gets a clean and light interface. Iconic behavior, honestly πŸ‘‘

AirInvServer accepts the following options:

  • --prefix β€” Shows the AirInv installation prefix πŸ“
  • -v, --version β€” Prints the currently installed version of AirInv to the standard output ✨
  • -h, --help β€” Shows that help message and displays usage πŸ’œ
  • -b, --builtin β€” The sample BOM tree can be built-in or parsed from an input file. If you go the input file route, you have to pass it with either the -i/--inventory option or the -s/--schedule and -o/--ond options together 🧚
  • -f, --for_schedule β€” The BOM tree gets built from a schedule file instead of an inventory dump πŸ¦‹
  • -i, --inventory <path-to-input-file> β€” The path (absolute or relative) to the (CSV) input file that describes the inventory (flight-date) details πŸŽ€
  • -s, --schedule <path-to-input-file> β€” The path (absolute or relative) to the (CSV) input file that describes the network/schedule (flight-period) details 🌈
  • -o, --ond <path-to-input-file> β€” The path (absolute or relative) to the (CSV) input file with the O&D (origin/destination) details πŸ’…
  • -y, --yield <path-to-input-file> β€” The path (absolute or relative) to the (CSV) input file with the yield rule details πŸ”₯
  • -t, --protocol <server network protocol> β€” The server protocol 🫢
  • -a, --address <server host address> β€” The server address 🌸
  • -p, --port <server host port> β€” The server port πŸ’–
  • -l, --log <path-to-output-log-file> β€” The path (absolute or relative) to the output log file πŸ“
Want the defaults? Run AirInv --help and it'll show you all the default options. No cap, that's the move πŸ’€

✨ SEE ALSO ✨

Your next reading list, bestie πŸ“š: airinv(1), AirInvClient(1), airinv-config(1), airinv-library(3) 🧚

✨ SUPPORT ✨

Found a bug? Report it! Send it to https://sourceforge.net/apps/trac/airinv/report πŸ™ˆ

Copyright © 2009-2011 Denis Arnaud 🌈

For more on the (LGPLv2+) license, check the COPYING file, or read it online at http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html ⭐


Okay that's the whole page, bestie 🫢 Shoutout to My Project for the source, and to AirInvServer(1) for being an absolute main character πŸ‘‘πŸ’–

πŸ“¦ where this page comes from