Sidecar Applications
Sidecar Applications
Sidecar Applications are placed near the Voedger executable and deployed automatically when VVM starts
Naming: after Sidecar Containers
VVMConfig.DataPath
📂apps
📁app1Owner.app1Name
📁image // unzipped app image, the same structure as baseline, see https://github.com/voedger/voedger-internals/edit/main/framework/vpm/baseline.md
descriptor.json
📁app2Owner.app2Name
📁image // unzipped app image
descriptor.json
Related issues:
Functional design
Place sidecar app files in
$dataPath/apps/
Provide
$dataPath
value in the--data-path
command line argument of the host applicationLogging:
sidecar app <app name> parsed
Technical design
VVMConfig.DataPath
provideSidecarApps()
builds all sidecar applications ifVVMConfig.DataPath
is specified
Testing
Limitations
Currently, the following names for sidecar applications are allowed:
test1/app1
test1/app2
test2/app1
test2/app2
data of a sidecar application can not be updated by VSqlUpdate
Last updated
Was this helpful?