Ignition Edge deployment best practices

Hi Guys

As what i know, Edge only allow to import the project/tag/image via designer.
I have multiple Touch panel running Ignition edge. My plan is develop the project using laptop(Standard Ignition) and import into the Touch Panels (Ignition Edge).

What is the best practices to deploy the project remotely?(from Stand ignition to edge ignition)

The best practice is to not do that. Develop in another copy of Edge. (Don't run gateways directly in your laptop. Use VMs or docker containers. Make as many VMs as you need for various target environments.)

2 Likes

Agree w docker approach. It is a bit of a learning curve to get the environment set up, but once you have your containers running they are standalone instances that can be fully backuped up & restored very easily.

1 Like

Hi

Thanks for the suggestion. understand using VM to develop the edge may be the best approach instead of develop on standard ignition edition.

I would like to know how to deploy the Ignition Edge project into a Touch Panel. Based on what i know, edge only can import via designer, But we no need to develop the project on the Panel, it feel like install the designer just for import the project.

What i current practice is

  1. export the project into thumb-drive
  2. then transfer the project from thumb-drive to the Touch Panel
  3. import the project on Panel environment via Designer

It is very inconvenient for project update. Can we transfer the project remotely just like FTView?

If you design in Edge, you can do a full gateway backup just like you would with Standard and restore it to another Edge system, all through the Gateway webpage.