locodb:locodb-en
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| locodb:locodb-en [2025/10/16 12:21] – [Locomotive] rjversluis | locodb:locodb-en [2025/10/19 14:13] (current) – rjversluis | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======Locomotive | + | ======Mobile |
| [[: | [[: | ||
| [[:english | Content ]] -> [[: | [[:english | Content ]] -> [[: | ||
| * [[: | * [[: | ||
| - | * **[[: | + | * **[[: |
| \\ | \\ | ||
| - | |< >| | ||
| - | | Short hand for //" | ||
| \\ | \\ | ||
| =====Description===== | =====Description===== | ||
| - | The idea behind the LocoDB is to be able to access all locomotives on all computers with access to the same NAS/Cloud storage.\\ | + | The idea behind the LocoDB/ |
| Even with an offline Rocview it will be able to access the locomotives and check their properties.\\ | Even with an offline Rocview it will be able to access the locomotives and check their properties.\\ | ||
| + | ====R/W Access==== | ||
| + | Without read and write access of the RocrailDB this concept will not work.\\ | ||
| + | |||
| \\ | \\ | ||
| =====Structure===== | =====Structure===== | ||
| - | The LocoDB | + | The Database |
| Every loco has its own directory named by its ID. Blanks are replaced with underscores; | Every loco has its own directory named by its ID. Blanks are replaced with underscores; | ||
| - | ====Example==== | + | ====Tree==== |
| - | This is an example of a LocoDB on a NAS:\\ | + | |
| - | {{: | + | |
| - | + | ||
| - | ===Tree=== | + | |
| < | < | ||
| - | LocoDB | + | RocrailDB |
| - | ├── | + | ├── |
| - | │ ├── | + | │ ├── |
| - | │ ├── | + | │ │ ├── backup |
| - | │ └── | + | │ │ │ └── 20251017162241462-EssoTank.xml |
| - | ├── | + | │ |
| - | │ ├── | + | │ |
| - | │ └── | + | │ |
| - | . | + | │ |
| - | . | + | │ │ ├── Frico.xml |
| - | . | + | │ |
| - | ├── | + | │ |
| - | │ ├── | + | │ |
| - | │ └── | + | │ |
| - | └── | + | └── LocoDB |
| - | ├── DB100.png | + | ├── BR01097 |
| - | ├── m3072.png | + | │ ├── backup |
| - | └── V1002215.xml | + | │ │ ├── 20251016161334845-BR01097.xml |
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | ├── BR120119-3 | ||
| + | │ ├── BR120119-3.xml | ||
| + | | ||
| + | | ||
| + | . | ||
| + | . | ||
| + | └── V1002215 | ||
| + | | ||
| + | ├── m3072.png | ||
| + | └── V1002215.xml | ||
| </ | </ | ||
| Line 63: | Line 76: | ||
| ====Setup Path==== | ====Setup Path==== | ||
| {{: | {{: | ||
| + | The group field can be used as filter.\\ | ||
| \\ | \\ | ||
| Line 73: | Line 86: | ||
| \\ | \\ | ||
| =====Locomotive===== | =====Locomotive===== | ||
| - | For selecting a locomotive from the LocoDB the " | + | For selecting a locomotive from the LocoDB the " |
| + | ====Workspace==== | ||
| + | The Workspace field accepts a CSV list of multiple names.\\ | ||
| + | The group field can be used as extra filter.\\ | ||
| + | Example: | ||
| + | < | ||
| {{: | {{: | ||
locodb/locodb-en.1760610096.txt.gz · Last modified: 2025/10/16 12:21 by rjversluis