Thanks through the commandline version, OOBD can run on embedded systems as a normal web server service, fully controlled just over the users browser.

This feature is still in beta, the actual installation process can be found on Github

This page mainly documents the planned startup cycle.

Legend

<graphviz dot right> digraph finite_state_machine { # rankdir=LR; # size=“9,5”

  node [shape=circle style=filled];
  Fn [ label = "Function" fillcolor= green];

  node [shape=box style=filled]
Tb [ label = "White\nnothing done yet" fillcolor= white];
Tr [ label = "Orange\nconcept & studies" fillcolor= orange];
Ty [ label = "Yellow\nPartial / Beta" fillcolor= yellow];
Tg [ label = "Green\nin use" fillcolor= green];

} </graphviz>

The actual planned Startup- Sequence:

<graphviz dot right > digraph finite_state_machine { # #rankdir=LR; # size=“9,5”

      node [shape=circle style=filled];

      F1 [ label = "oobdd w.\nbuild in scripts" fillcolor= green];
      F2 [ label = "oobdd w.\nexternal scripts" fillcolor= yellow];
      F3 [ label = "oobdd w.\nexternal settings" fillcolor= yellow];
      F4 [ label = "oobdd w.\nstartup script" fillcolor= yellow];
      F5 [ label = "python w.\quickscript" fillcolor= white];
      F6 [ label = "python w.\nisoTP\nsocketCan" fillcolor= orange];
      F7 [ label = "own shell\nscript" fillcolor= green];

      node [shape=box style=filled]

T1 [ label = "/media/usb?" fillcolor= green];
T2 [ label = "autorun.sh?" fillcolor= green];
T3 [ label = "autorun.py?" fillcolor= white];
T4 [ label = "autorun.xml?" fillcolor= white];
T5 [ label = "autorun.lua?" fillcolor= white];
T6 [ label = "settings.json?" fillcolor= white];
T7 [ label = "/scripts?" fillcolor= white];

T1 → T2 → T3 → T4 → T5 → T6 → T7;

T1 → F1 [ label = “n”]; T2 → F7 [ label = “n”]; T3 → F6 [ label = “n”]; T4 → F5 [ label = “n”]; T5 → F4 [ label = “n”]; T6 → F3 [ label = “n”]; T7 → F2 [ label = “n”]; }

</graphviz>