Just to clarify - The suggestion from 4D Technical Support is to include 100% of the entire application package that is built by 4D. Typically this is done by archiving the application in a ZIP file or on a DMG and transferring the archive to the destination machine where it is unarchived. You can go a step further an use an installer also.
In a situation where there is limited bandwidth (if you feel that transferring the whole package is too much), then as an alternative you can try to use a product like RSYNC or ROBOCOPY. Using these 3rd party tools you can skip the files that are identical between the source and destination, and only transfer the files that are different. Typically doing a transfer in this way would include more than just the 4DC. The overall goal of both approaches is to get the application to the destination machine in a way that makes it so that the files running on the destination machine match the files that were built. -Tim > However, I found another issue, the backup settings and maybe the cache > settings were not set on the deployed server deliverable and I set these > manually. How do you manage these settings? Using "User Settings" allows you to manage the cache settings in an external file at the deployment site: http://doc.4d.com/4Dv15/4D/15.6/Using-user-settings.300-3836796.en.html However the backup settings are not included in user settings... So you can manage the backup xml file as outline in the following tech tip: Tech Tip: Retaining the Backup Settings when upgrading a merged application http://kb.4d.com/assetid=77988 -Tim ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
