On Oct 16, 2018, at 2:00 PM, Robert wrote: > I recently started to use built client/server more often since I inherited a > client that was already doing that. I was told by another developer that when > doing a structure change that I can simply swap the .4DC file and I’m done. > 4D TS suggests that this is not wise and that I should probably use rsync or > simply supply the whole built client each time. So, what do you do?
Hi Robert, The “Best Practice” is to do what 4D TS says — update the complete package and don’t fool with individual files. But I — and many others — live dangerously because we think we know what we are doing, are willing to suffer the consequences when we screw up and want to do a faster manual update of an application. If you know that all you have done since the last deploy is edit the .4DB in the Design environment adding and editing forms, methods and things in the Tool Box (excluding Resources) and the structure, then the only thing that will change when you do a build is the .4DC and .4DIndy. I have one client that I do this for constantly. Done it probably over 50 times over the years. Never a problem that I didn’t create by not following the above rule. I have another client that I NEVER do this for. I’ve got a very easy to use auto update system in place and it is actually easier and faster to just replace the complete application package with each update. (If I ever find the time and get motivated, I’ll create a system to do this for the first client.) > Also, when building the built client/server do you use the 4D commands with > the XML project or do you use the GUI? > > I was happily using the GUI and editing the engined server link file in the > client such that it points to the correctly deployed server as it defaults to > the local development server….. 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? I use a hybrid system. I first use the Build dialog to set everything that I can and then do a test build to prove that it works. Then I have a “Build Application” method that takes the BuildApp.xml file from the dialog and adds all the custom build keys that I need to do a deployment build. For backup settings, you have to find a way to copy the current “Backup.xml” file from the installed version to the new version. One way is to script that during the installation of the new version. Might be a way to automate creating this file during a build, but you would have to communicate with the running 4D Server somehow and extract the needed information and then manually build Backup.xml so that it was identical to the one on the server. Put that in the right location in the new version. Backup settings and the “Log” folder is one of the reasons why for the one client I just install the .4DC and .4Dindy. Then I don’t have to worry about copying these things from the old version to the new version. For cache settings just turn on the Database Settings -> User Settings on the machine and it takes care of itself. Tim ***************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ***************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
