commit | 62c416fb0d2f62e09d7f60754ff359ac2389e749 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Wed May 18 15:34:25 2022 -0700 |
committer | Ed Tanous <ed@tanous.net> | Tue May 31 16:30:10 2022 +0000 |
tree | 9b69d5294fd5c45bda8e691453e2cc96524bf94f | |
parent | a43ea82f71c6eaeeae8f28d0b0179d489decfd81 [diff] |
Document prior experiences with headers Several developers have spent time on the problem of "bmcweb makes too many uses of headers". This document is to attempt to document those cases, such that others don't duplicate time. If this document is successful, it will eventually be deleted when we solve this issue. Tested: Documentation only. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I64c84100abbf542d68925060c2f4fe6f6bff1402
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 -C builddir test ninja -C builddir coverage
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.