commit | 929d4b57f10bc4200e16b71fbcf32521d8cc23c1 | [log] [tgz] |
---|---|---|
author | Gunnar Mills <gmills@us.ibm.com> | Fri Nov 13 09:35:30 2020 -0600 |
committer | Gunnar Mills <gmills@us.ibm.com> | Fri Nov 13 16:17:17 2020 +0000 |
tree | 3540a2df01041e22b82e045dcfe8089ff21d7b97 | |
parent | 3a17e02873fdf53898a2cfce894dcb36223d76d4 [diff] |
Common Errors: Fix list formatting Pretty sure the author wanted these on separate lines so do that. Makes the list a lot easier to scan. Could have done this multiple ways but went with bullets. Fixed an escape. Tested: https://jbt.github.io/markdown-editor/ Change-Id: Ia0a0e5a2023f7eebda1ebf2d4d1d6528429cce8c Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
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 -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.