Is it me or has the default deployment operation changed from migrate to install/replace? (could be just me miss-remembering)
however - could there be a bulk option to switch the operation. I have more files being migrated than being replaced or installed. By way of belts and suspenders a migration is safer to preserve data. Plus if the file doesn’t exist it would reject the migraiton option.
Also one other question on a build operation when you choose copy is it also possible to also include the clone as well - just incase you wish to migrate vs replace?
OttoDeploy attempts to figure out the default based on the files present on the destination server. If the file exists on the destination it defaults to Migrate, otherwise it defaults to Install/Replace. I will double check that this behavior is still working, its not impossible that it may have been changed.
I have recently been testing Otto 4 for an upgrade of Otto 3, and so far, the multiple installs have defaulted to Copy, not Migrate, even though the files were the same on both servers.