I have OttoFMS installed on a Mac, not connected to the Internet. I just did an uninstall/install of the latest OttoFMS (4.15.1). I thought clicking the blue Update Available button in OttoDeploy would get it from OttoFMS, but it just spins like it’s trying to reach the Internet.
I downloaded the OttoDeploy.fm12 file from the site. I assume it gave me the latest and greatest version. If I simply replace my existing OttoDeploy file on the server, will it still retain all the stuff previously set up? Or should I rename the new file and perform a migration? (Seems like extra steps!)
For OttoDeploy to autoupdate in place it needs to have a connection to the internet. It downloads the latest copy of the html and installs it in the file. But I think you must have a connection to the internet to download the file. So I am not sure why it’s just spinning for you. Can you clarify?
If you just replace the file on your server with the latest version from us you will loose your setup. OttoDeploy is just a FileMaker file. The data is stored in regular old tables and fields. So you if you replace it, your will wipe your data. You can do a migration that will work fine, if you need to go that route.
I downloaded the file on a separate computer, to transfer via USB.
I tried the blue update button thinking that if you could install OttoDeploy the first time from OttoFMS, maybe the updated OttoFMS would somehow contain the updates for OttoDeploy as well.
A migration would certainly work, but you may find it easier to just update the HTML manually. If you search for the script named get latest production app within OttoDeploy, you can see that all it’s doing is downloading some HTML to the text field System::AppHTML. If you could just get that HTML into your environment some other way and update that field, you’ll be good to go!
Note: This method won’t work if you need a “schema upgrade” and for this a migration is required anyway. You can check the global var $$schemaVersion that is set in your old copy of OttoDeploy. As long as this number is the same as the first number of the version you are downloading (version 2) then updating the HTML field is all that’s needed.