Hi I found out that when build an App connect web app for a certain website, certain settings are written to config.js in the dmxAppConnect folder. I upload my application and all the dmx folders and it works fine.
But I sometime develop other App connect apps for a different website and afterwards I like to use this some of these Apps for the first website. I copy the App pages and the subfolders from dmxConnect folder to the first website and upload.
But now my question: the first website has a config.js in the dmxAppConnect folder with different content than the config.js file present in the other website(which has many more Apps) What to do? Is the config.js file an obligated file, or can I jus leave it and not upload it?
Thank you for your reply Teodor. But if I understand correctly, uploading a different config.js file (from my development site) to a production site (which has also other app connect apps, not present in my development site), will overwrite the existing config.js and thereby the stored query parameters will be lost. The existing apps on the production site will not find the stored query parameters. That will cause problems, maybe not break my site, but it will break some functionality.
Isn't it more logical that the query parameters are stored in an App specific config.js, so each App has its own config.js. If above conclusion is right, than the current setup does not contribute to portability in my App development workflow.