OttoDeploy version 2.0.0 Released!

OttoDeploy
1

Hey y’all,

OttoDeploy version 2.0.0 was just released! This is our first Schema change for OttoDeploy since our initial release, so its a big deal. This update adds some features which have been missing for a while (finally, a default file location!!), and extends the capability of OttoDeploy by letting you add servers directly from the Ottomatic Cloud Console!

This version also fixes a variety of bugs reported by y’all and adds support for the new pre-deployment scripts released with OttoFMS version 4.7.0. You can check out the full list of changes in the changelog.

Updating OttoDeploy this time will be slightly more complex than normal, as you’ll need to provide OttoDeploy its location and credentials. You can click the button that appears in the sidebar the next time you open up OttoDeploy, and it will prompt you to select the server where OttoDeploy lives, as well as the username, password, and encryption key for the file. This will be used to kick off a deployment from our remote build of OttoFMS 2.0.0 which will migrate all of your deployments into the new copy of the file. If you have any issues with the deployment let me know here!

As always, let us know if you have any issues updating or running the new version. Thanks y’all!

-Kyle

4 Likes
2

URL for direct download of OttoDeploy V 2 not working- 404 error
https://appupdates.geistinteractive.net/ottodeploy/fm-builds/2/OttoDeploy.fmp12

3

Sorry about that, just fixed it

-Kyle

4

Does OttoDeploy 2.0 work with previous versions of OttoFMS or should we wait to upgrade until OttoFMS is on v. 4.7

5

It still works with previous versions of OttoFMS! There is a new feature in there that will work with 4.7.0 (pre-deployment scripts), but that will be greyed out if your destination server is not 4.7.0.

-Kyle

6

Edit: Entirely my fault, forget it.

STRIKETHROUGH: We have our own encryption key for otto. Sadly this prevent the auto update (encryption key false). How should one go about it?

7

When you click the button in OttoDeploy to run the update it should let you enter your encryption key for the file. This is used to set up the deployment to migrate to the new version of the file. Are you not seeing the option to enter your encryption key?

-Kyle

8

As edited previously it was entirely my fault :sweat_smile:
It works perfectly fine!

1 Like