Replies: 3 comments
-
|
I don't every want to sync stuff to a cloud platform anyway. What I do like is a way to export/import my configuration (including secure values) from one machine to another, or between OS installs. Hoppscotch for example allows me to export collections. The one thing I don't like there is that it tries to hide the file system from me. A nice in-between could be having a custom format for export/import which may or may not exclude sensitive data. This could tailor to people who don't want to fiddle with filesystem operations and want to keep everything inside of MQTT Viewer. But, add to this a way to simply copy/backup a configuration directory and I'd be happy, too. |
Beta Was this translation helpful? Give feedback.
-
|
If you were to commercialise this I suspect this would be a good feature for the "pro" version, but the strenght I can personally see in this app is is dropping it in to find out what something existing is doing. So as above, some way to export/import settings or even just have the settings in a suitable file alongside the exe so it can be copied around very easily would be good. Doesn't need any cloud for that |
Beta Was this translation helpful? Give feedback.
-
|
Hey @samfweb trans feature would be highly useful in the scenarios I use this for. I understand that there is interest in a loud and non cloud reliant approach ? Nats server can probably be a good solution . for web that is real time synced so that teams can see all changes occurring I use Datastar. It can use nats to sync the data between leaf nodes. here is a super simple example to show how the web gui can update if something happens on the backend : https://github.com/starfederation/datastar/tree/develop/examples/go/hello-world itβs very much architecture independent, and so might be a useful approach . feel free to contact me if you need to chat .. I have used this for a ton of projects and itβs been wonderfully simple but potent to get projects spun up . |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Message collections is currently in-progress, however I've realised that teams with many engineers might benefit from sharing their message collections / connections securely using a cloud instance.
I'd rather not handle any sensitive date like passwords or certificates so I'm leaning towards leaving those fields local-only.
Example connection scenario:
Example collection scenario:
Beta Was this translation helpful? Give feedback.
All reactions