commit | c5114a57c5460916141260b5d31680f82fdda324 | [log] [tgz] |
---|---|---|
author | Josh Lehan <krellan@google.com> | Thu Mar 03 18:25:55 2022 -0800 |
committer | Ed Tanous <ed@tanous.net> | Sat Mar 12 18:17:22 2022 +0000 |
tree | dd78a6d266fe469f0a50ce337e252c72a82452f8 | |
parent | f7725d79fa9b5fcffcc368008fa029ea1a16c4b9 [diff] |
Updated text to elaborate on JSON exceptions Mentioning operator<< and operator>> as throwing Noting preferred usage of parse() and dump() Signed-off-by: Josh Lehan <krellan@google.com> Change-Id: I1ffdc4b39e518ec348a553eac5080accf75fae8e
This component attempts to be a "do everything" embedded webserver for openbmc.
At this time, the webserver implements a few interfaces:
BMCWeb is configured by setting -D
flags that correspond to options in bmcweb/meson_options.txt
and then compiling. For example, meson <builddir> -Dkvm=disabled ...
followed by ninja
in build directory. The option names become C++ preprocessor symbols that control which code is compiled into the program.
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C buildir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in bmcweb/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja coverage -C builddir test
When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.
When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the secp384r1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.