OttoFMS 4.10.0 was just released!! This is one of our biggest versions to date, bringing a brand new Builds UI, Webhook based Deployment notification, zipped offsite backups, and a ton more. I’ll list the big highlights below, but you can see the full changelog here. This version brings:
A builds UI in the OttoFMS console (and the Ottomatic Cloud Console!) which lets you see a history of builds, rerun builds, and manage builds in your Outbox.
Build scheduling
Webhook based deployment notifications
Zipped offsite backups
A bunch of new APIs for deployment, build, and setting management
Easier webhook authentication using the data api key in the path
A new deployment source type which lets you pull files from any url (even ones OttoFMS didn’t build)
a variety of new safety nets around the FMS Admin API
Bug fixes galore!
Check out the updating docs for details on getting started with the new version, and as always, let us know if you have any issues installing!
As a quick note without a lot of research, I just updated a server to 4.10 and now I can’t log into Otto on that server with the proper username and password, even though it works with the admin console, so now I’m going to find the instructions on downgrading the version–more info to come, I’m sure.
–simply backing down to 4.9 didn’t fix it
–Backing down and then rebooting, did fix it
Kyle, I just rebooted the entire server. Yes it was really weird. This was all so I could do some re-naming of files. We had talked about this previously, and I thought you had added that feature but I…hadn’t found it. So I tried doing it with the command line to great failure. In my mind the FMDeveloperTool --renameFiles, is a big steaming piece of uselessness and wasted time.
After I did All this I finally found where y’all hid it the feature. I thought I might give it a try, then decided “no.” I didn’t want to experiment anymore. So the files got shipped down via Transmit, then dropped into the FileMaker Developer tool in FileMaker and names were changed. They are now uploading.
This particular task was the removal of spaces for two particular files–but not other files. For this client there are 85 files. Fortunately, I only had to deal with 14.