Simulink Configuration Parameters Edit This list describes how the configuration is used. Many options include: { “name”: “X-Django”, “description”: “X-Django and X-MongoDB Compile”; “server”: [“Apache HTTP Public Server”, “GitHub”, “http://gitengine.org”], “redhat”: “3.5.0”, “factory”: “Apache-2.4.2”, “siteport”: 8080, }) Use of this configuration will add a default server that only uses HTTP and not a proxy for HTTP. The information stored in one repository is retained. If your production sites use Apache HTTP, the default repository will use the default server. If not, the default repository may use a public HTTPS proxy. A default repository may use the default server on different sites. If a custom proxy server is enabled or disabled, then the HTTP proxy configuration will override the default. { “default”: true, “server”: “http://localhost:7777”, “redhat”: true, “localhost”: 877, } On a production site, only you and the author of the project are allowed access to the default server. Also, if this configuration is used on a production site, or if you use a custom proxy which is not enabled in production, the default servers of production and all others that use PHP will not work. The default public url used by default for a given repository will default to http://localhost:8000/site. In-memory changes: server: { “login”: “[email protected]”, “statusCode”: “5”, } On a production site, if you need to modify the default website, you cannot do this. In fact, modifications of this configuration will be ignored by HTTP proxies. Options: The following configuration supports two default servers: