Method for Common Development across Multiple Applications

Help
,
1

I have two applications today, one that represents devices in a production fleet, and a second that represents a development fleet. I think I’d like to develop workflows/dashboards/experiences. in the development application, where there is little risk of disturbing the production environment, and export/import the latest releases to the production application once new workflows/dashboards/experiences are ‘ready for production’

Is the concept of keeping dev and prod as separate applications flawed? I can appreciate the effort taken to create version control at the workflow/etc level inside a given application, and don’t want to create a design that is counter to Losant’s intended implementation.

2

You are referring to what we call “Application Lifecycle”, which uses the export/import features exactly as you described. In most cases, application lifecycle replaces the per-resource version control features. We have a full guide here:

3

Brandon, this is exactly what I was looking for. I had noticed the exported files were organized super-convenient for use with GitHub; now I see that was totally intentional. This was a good read, thank you for the response.