Skip to content
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

Development Environment in Dashboards #10781

Open
nicovon24 opened this issue May 14, 2024 · 2 comments
Open

Development Environment in Dashboards #10781

nicovon24 opened this issue May 14, 2024 · 2 comments
Assignees
Labels

Comments

@nicovon24
Copy link

Hello,
I am encountering an issue within my current company regarding the absence of a development environment in Thingsboard. Unlike my previous experiences in various courses and companies where I had the opportunity to work with development environments, Thingsboard lacks this crucial feature.

My current workflow involves creating both production and development dashboards. However, this approach is inefficient and prone to errors. I find myself having to manually transfer changes from the development to the production environment, often resulting in oversights or missed updates in the process.

This inefficiency was recently highlighted when presenting the application developed with Thingsboard to a respected tester. He expressed dissatisfaction with our approach, particularly our use of client dashboards in the production environment.

Given that popular platforms like GitHub and many open-source projects provide development environments, I strongly believe that Thingsboard should offer a similar feature. Such an environment would greatly streamline our workflow, ensuring smoother transitions from development to production and less errors with our clients.

In addition to that, it would also provide a more modern software development environment and more people would be interessed in the platform, we have more than 700 devices and 20 really relevant dashboards and an error in production could cost my company a client, in a thing which could be detected in development and testing side

Thanks!

@devaskim
Copy link
Contributor

Hi @nicovon24
In general, I agree with you that it is very serious questions. However it is not clear at least for me what you want to get from the TB development environment. So maybe try to describe your ideas in details

@nicovon24
Copy link
Author

nicovon24 commented May 14, 2024

Hello!
Currently the platform is not using Agile methologies for developers of the application, it is using "live development" which is when you work always in production. Which leaded us to many errors with clients.
I suggest implementing a branching system similar to GitHub for dashboards, allowing for separate development and production versions. While I understand that this feature is currently only available for backup recovery in the platform using GitHub, having it directly in the dashboard and others like rule chains, this functionality would be beneficial. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants