Feature/custom model editor

[ditschi]

This Adds

• tonies.custom.json save API with validation and backups
• custom_img root support for image workflows

I also removed built web assets from teddycloud_web submodule -- i assume that was added by accident?!)

REQUIRED BY: Web changes from toniebox-reverse-engineering/teddycloud_web#283

Preview -- what will these backend changes make available in web

Custom Tonies Editor: Editor for managing custom tonie models

Settings: Enable/Disable Editor -- (changes menu entry from WIP: Add Model to Manage custom models

Custom tonies editor Manage custom models

Image Manager:

Shared UI for selecting and managing images in TeddyStudio and Custom Tonies Editor

Image Editor::Default Images

Image Editor::Upload and manage Custom Images -- also available in Tonie Studio

[SciLor]

Please use the web repo for the web stuff.

[ditschi]

Please use the web repo for the web stuff

Sure .. Second PR will be created for submodule changes

[SciLor]

Please also remove the compiled web changes (contrib www)
This will be done later by the pipeline.

[henryk86]

This would solve the following issues:

• Symlink to custom_img in library folder #280 (Not necessary anymore)
• Feature: Provide API to get an existing entry of the tonies.custom.json #178
• Feature: API to extend Tonies.custom.json #176

[ditschi]

Please also remove the compiled web changes (contrib www) This will be done later by the pipeline.

removed and added to .gitignore.

[SciLor]

Please don't add it to the .gitignore
It should be in the repo, but not committed manually. The pipeline does.

Also don't commit the submodule changes of _web into this repo

[ditschi]

Removed contrib/data/www/ from .gitignore.

I’d like to clarify the workflow so I can document it for contributors. I assumed I had to update the teddycloud PR with the teddycloud_web merge commit (after PR #283 is merged) before merging the main PR. Your comment suggests I should not commit submodule changes in this PR.

Questions:

Is the intended flow: merge both PRs separately (web first, then backend), then a maintainer updates the submodule pointer?
I couldn’t find this workflow documented in the README or elsewhere. Would it be okay if I add a short section (e.g. in README or a new CONTRIBUTING.md) for future contributors?
Thanks for the clarification.

[henryk86]

Have a look into the actions. As far as I know it’s a mix of manual execution and automation:

https://github.com/toniebox-reverse-engineering/teddycloud/actions/workflows/build_commit_web.yml

and then a commit into develop starts automatically https://github.com/toniebox-reverse-engineering/teddycloud/actions/workflows/publish_docker_matrix_all.yml which generates the docker images.