aboutsummaryrefslogtreecommitdiffstats
path: root/src/libcommon/gsm_data.c
diff options
context:
space:
mode:
authorOliver Smith <osmith@sysmocom.de>2019-12-02 15:02:22 +0100
committerOliver Smith <osmith@sysmocom.de>2019-12-03 11:41:21 +0100
commitad08d17e07f307fbb67492707017a3d5103f1683 (patch)
tree257de745d22d081b018a4be261ef9e9e52f7bb7a /src/libcommon/gsm_data.c
parent118c411e81d6a3aa96a721beab937a361fa5d551 (diff)
regen_doc.sh: support gbproxy, run without docker
Do not only update the VTY reference and counters of osmo-sgsn, but also the VTY reference of gbproxy. This was not possible with the old code path of calling "regen_doc.sh" inside docker-playground.git, as it expects the program to be updated to have the same name as the docker image. Using the docker-playground script also has the disadvantage, that one must push the development branch to git.osmocom.org before updating the VTY reference/counters, because that script would build a new docker container with a freshly cloned repository, check out the same commit that we have already locally, build that and then finally regenerate the docs. So instead of adding another parameter for the docker image to the script in docker-playground.git and calling it twice, simplify the process by rewriting the regen_doc.sh script in osmo-sgsn.git. Make it start the locally installed osmo-sgsn and osmo-gbproxy binaries and call osmo_interact_vty.py on them. Related: OS#4292 Change-Id: I8b5bd5347ea34266ad650383372630f2a84d5cce
Diffstat (limited to 'src/libcommon/gsm_data.c')
0 files changed, 0 insertions, 0 deletions