[Question] How do I activate the gateway Developer Mode?

Ignition
1

My gateway is 8.1+ running with the trial license. I’m trying to activate Developer Mode so I don’t have to sign the .modl files before installing them.

Thank you!

2
1 Like
3

Hello Kevin,
I just found what you said in Ignition Maven Plugin v1.0.11 Fails - #3 by xasga and yes but I suspect I didn’t do it properly because my gateway isn’t in developer mode. This is what I added to (the 3rd line) .conf, I assumed it must follow the same pattern.

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=com.inductiveautomation.catapult.Catapult
wrapper.app.parameter.2=Dia.developer.moduleupload=true

[edit] Dang it, I need to read more carefully…I didn’t set the parameter as Kevin said.

4

You need to follow the pattern (and use the same parameter name) as in Kevin’s linked post:
wrapper.java.additional.7=-Dignition.allowunsignedmodules=true

wrapper.app.parameter is the wrong section of the configuration file, D is the wrong prefix (should be -D), and ia.developer.moduleupload is the wrong flag.

1 Like
5

Thank you Mr. Griffith.

6

I’m having a very difficult time getting this to work properly in a Docker container. The first time I set it up, everything worked flawlessly. The second time, I experienced issues for about an hour before it suddenly began working without any clear changes on my end.

However, with the third and fourth containers, the parameter updates are not being applied or recognized at all.

Has anyone experienced similar behavior or have any insight into what might cause containers to ignore updated parameters?

Current parameters:

# Java Additional Parameters

wrapper.java.additional.1=-Ddata.dir=data
wrapper.java.additional.2=--add-opens=java.base/java.lang=ALL-UNNAMED
wrapper.java.additional.3=--add-opens=java.base/java.io=ALL-UNNAMED
wrapper.java.additional.4=--add-opens=java.base/java.security.cert=ALL-UNNAMED
wrapper.java.additional.5=--add-opens=java.base/java.util=ALL-UNNAMED
wrapper.java.additional.6=--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED
wrapper.java.additional.7=-Dignition.allowUnsignedModules=true
wrapper.java.additional.8=-Dignition.developer-mode=true

7

This is the only relevant parameter, and AFAIK it's case sensitive, so you should define it as -Dignition.allowunsignedmodules=true.

Restart the Gateway for changes to ignition.conf be picked up.

3 Likes
8

If you're using Docker, you don't have to worry about trying to edit the data/ignition.conf. Instead, consider supplying those JVM arguments in your container configuration. ref: Supplemental JVM and Wrapper Args