Document the configuration required for nested actions - $actionGroup and $actionGroupSubTitle

After changing name of node in dataflow, access name from script is still same.

In the last instruction in the docker file you wrote :

RUN bin/users.sh add -u myuser -p mypassword

but when I log to the server and do a ls in /app/bin there is no users.sh file just users.dart file

Thanks.

I'm using some of the instructions in the wiki page for creating and running a Docker container. The wiki states to add a user you run the following:

Add a user.

RUN dart bin/users.dart add -u myuser -p mypassword

...how can we customise this so that:

• We can create super users (or just normal users)
• Set the rootUrl
• Set whether the user can use the designer
• Set permission groups

Also how can we pass the password in so that it isn't in plain text? (or so that needs to be changed on first login)

I tried to include in my custom image the following instructions

WORKDIR /app
ADD conf/server.json .
ADD conf/certs certs

But when the server is launched those files are overridden.
I tried to put in /data but when the volume is mounted same problem appears.

To setup LDAP Authentication in DGLux Server, add the following to your server.json:

  "ldap": {
    "url": "ldap://myhost.org",
    "dn": "cn=root,dc=myhost,dc=org",
    "password": "MyPassword",
    "searchBase": "dc=myhost,dc=org",
    "groupAttribute": "gidNumber",
    "superuserGroup": 0
  }

Currently, attributes are not typed. That is not an issue for attributes that are set programmatically through an SDK. However, because DGLux allows for a user to manually set attribute values, it means an unconscientious user could set the attribute to a value incompatible with its intended type . Therefore, handlers that deal with set operations on attributes must implement type error checking to account for DGLux which would otherwise not be necessary (i.e., if attributes had a type which DGLux could "read" and therefore restrict the input).

In https://github.com/IOT-DSA/docs/wiki/Protocol%20Communication you say:

when in websocket mode, both client and server need to make sure a message is sent to other side at least once every 60 minutes, (because of network latency can cause message delay on other side, 30 ~ 45 seconds is suggested interval for a minimal interval)

if no message is received in 60 seconds, websocket should be considered disconnected and a re-connection is needed

The first paragraph should probably state "once every 60 seconds"

Where is the log? i can not find them