Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client | ||||||||
Line: 124 to 124 | ||||||||
| ||||||||
Added: | ||||||||
> > | Updated configuration file (as of 4-18-2024) | |||||||
Added: | ||||||||
> > | Beginning with version 6.2.0.24041811 (published on 4-18-2024), the Appx Server Connector configuration has been simplified and is now done with two files instead of three. Instead of modifying the files ‘appxConnector.js’ and ‘appxMongoConnector.js’ a single file is used for both and by default that file is named ‘default.json’. The file has two sections, one for each connector. The Appx Connector section is named 'appxConnectorConfig' and the Mongo Connector section is named 'mongoConnectorConfig'. Each section has a key/value pair where the key name is the same as the variable name that exist in the appxConnector.js and appxMongoConnector.js files as shown above and in the examples below. The default configuration file ‘default.json’ can be modified and used to configure the connectors as is but, the preferred method (since that file will be overwritten during a AppxConnector upgrade) is to use the ‘default.json’ as template in creating a file named ‘appxconnector.json’. f for some reason the configuration file needs to be named something other than ‘appxconnector.json’ or ‘default.json’, an environmental variable named NODE_CONFIG_ENV can be used to specify a different configuration file name. For example, setting NODE_CONFIG_ENV=MyConfig will cause each connector to look for a file named ‘MyConfig.json’ on startup to configure that connector. | |||||||
Here are a few common scenarios and their values.I want no reverse proxy, no encryption at all. ( Just a very simple configuration ) |