Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Pull Request Template
Title
Add ThingsBoard over HTTP
Type of Change
Description
Added support for automatically installing ThingsBoard CE when the Docker Compose stack is started. I introduced a new service called thingsboard-install, which runs ThingsBoard once with INSTALL_TB=true and LOAD_DEMO=true. This initializes the PostgreSQL database and sets up the demo dashboards and devices. After this service completes, the normal thingsboard-ce service starts and uses the initialized data.
This removes the need to run the manual installation command and allows the user to start PostgreSQL + ThingsBoard with a single docker compose command.
Testing
I tested the setup by starting the full stack with "docker compose --env-file .\config\services.env.template -f .\compose.services.secure.yml up -d thingsboard-ce". On a clean installation (empty data folders), ThingsBoard installed correctly, the demo data was loaded, and the thingsboard-ce service started normally afterward. I repeated the startup process to make sure the installation only ran once and that the stack behaved consistently.
Impact
[Discuss the impact of your changes on the project. This might include
effects on performance, new dependencies, or changes in behaviour.]
Additional Information
[Any additional information that reviewers should be aware of.]
Checklist
existing code.