laforge submitted this change.
docs/osmo-smdpp: restructure subsection "osmo-smdpp"
Sphinx is complaining about a duplicate label "osmo-smdpp". Apparantly
because we use this label twices as section headline. The subsection
"osmo-smdpp" in "Running osmo-smdpp" talks about the commandline and the
supplementary files that osmo-smdpp needs to run. Let's split the two
topics into two different sections.
Change-Id: I8bc4979160a00d36a03b9cd10679562a08c2c55c
---
M docs/osmo-smdpp.rst
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/docs/osmo-smdpp.rst b/docs/osmo-smdpp.rst
index dd44469..329b3d7 100644
--- a/docs/osmo-smdpp.rst
+++ b/docs/osmo-smdpp.rst
@@ -79,12 +79,8 @@
You can of course achieve a similar functionality with apache, lighttpd or many other web server
software.
-
-osmo-smdpp
-~~~~~~~~~~
-
-osmo-smdpp currently doesn't have any configuration file or command line options. You just run it,
-and it will bind its plain-HTTP ES9+ interface to local TCP port 8000.
+supplementary files
+~~~~~~~~~~~~~~~~~~~
The `smdpp-data/certs`` directory contains the DPtls, DPauth and DPpb as well as CI certificates
used; they are copied from GSMA SGP.26 v2. You can of course replace them with custom certificates
@@ -93,6 +89,13 @@
The `smdpp-data/upp` directory contains the UPP (Unprotected Profile Package) used. The file names (without
.der suffix) are looked up by the matchingID parameter from the activation code presented by the LPA.
+commandline options
+~~~~~~~~~~~~~~~~~~~
+
+osmo-smdpp currently doesn't have any configuration file or command line options. You just run it,
+and it will bind its plain-HTTP ES9+ interface to local TCP port 8000.
+
+
DNS setup for your LPA
~~~~~~~~~~~~~~~~~~~~~~
To view, visit change 38798. To unsubscribe, or for help writing mail filters, visit settings.