Skip to content

Update tonies-custom-json.md #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 1, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions content/docs/tools/teddyCloud/tecdoc/tonies-custom-json.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
---
title: "tonies-custom-json config"
description: "Info about the tonies-custom-json file"
title: "tonies.custom.json config"
description: "Info about the tonies.custom.json file"
bookCollapseSection: true
---
# tonies.custom.json
teddyCloud uses the tonies-custom-json file to read the metadata of custom tags in the same manner it's done for the official boxine tonies in the tonies-json file. The structure is the same, but it's not overwritten as the tonies-json file through regularly updates. So you can use the tonies-custom-json to save metadata of your own custom tags.
teddyCloud uses the `tonies.custom.json` file from `config` folder to read the metadata of custom tags in the same manner it's done for the official boxine tonies in the `tonies.json` file. The structure is the same, but it's not overwritten as the `tonies.json` file through regularly updates. So you can use the `tonies.custom.json` to save metadata of your own custom tags.

Initially the tonies-custom-json file looks like the following:
Initially the `tonies.custom.json` file looks like the following:

```
[]
Expand All @@ -16,7 +16,7 @@ In the GUI, a custom tag looks initially like:

![GUI](/img/tonies-custom-json_empty.png)

Enriched with metadata for the above shown custom tag the tonies-custom-json file looks like this (more details see below in section [Specification](#specification)):
Enriched with metadata for the above shown custom tag the `tonies.custom.json` file looks like this (more details see below in section [Specification](#specification)):

```json
[{"no": "0", "model": "123456", "audio_id": ["369519776"], "hash": ["af9e61a9c1b12138fb060908d595742334b04515"], "title": "Custom Tonie Example Title", "series": "Custom Tonies", "episodes": "This is my custom tonie", "tracks": ["Title 1", "Title 2", "Title 3", "Title 4", "Title 5", "Title 6", "Title 7", "Title 8", "Title 9", "Title 10"], "release": "0", "language": "de-de", "category": "custom", "pic": "https://upload.wikimedia.org/wikipedia/en/6/6b/Hello_Web_Series_%28Wordmark%29_Logo.png"}]
Expand All @@ -33,7 +33,7 @@ This results after restart of teddyCloud in the following changed appearance in

## Specification

The tonies-custom-json file uses the JSON Array Structure. It contains zero, one, or more ordered elements, separated by a comma. The JSON array is surrounded by square brackets [ ].
The `tonies.custom.json` file uses the JSON Array Structure. It contains zero, one, or more ordered elements, separated by a comma. The JSON array is surrounded by square brackets [ ].

Each element consists of a JSON object with the following keys:

Expand All @@ -57,4 +57,4 @@ Each element consists of a JSON object with the following keys:

Navigate to the taf file in the library (or content if library is not enabled) and double click on the row. A modal will be shown which contains the information:

![Getting the Audio ID and Hash value](/img/tonies-custom-json_getaudioid_hash.png)
![Getting the Audio ID and Hash value](/img/tonies-custom-json_getaudioid_hash.png)
Loading