Publishing Builds

While builds are useful on their source server, their purpose is truly to be a package of files which can be moved around. Deployments using Just In Time builds manage the movement of builds themself, but you can use publishing to more granularly control the distribution of builds to other locations or servers.

All builds can be published at the end of the build, simply define your publish destinations in the build settings in OttoDeploy. Builds can also be published after they are run using the Developer API.

Publishing to the source server's HTTP folder

Publishing a build to the source server's HTTP folder allows you to use the build as a public URL for deployments without having to manage a separate web server to host the build. Check out the Public Builds page for more details on what public builds are and why you might want them.

Publishing to a destination server's build inbox

Publishing a build to a destination server's build inbox allows you to skip the fetching process when running a deployment using that build. This is useful if you want to reduce deployment times. For an example of how to use this feature, see the Low Downtime Deployments guide.

Publishing to an offsite storage location

OttoFMS version 4.6.0 introduces the ability to publish builds to an offsite storage location. This can be useful for storing a library of previous application versions or for deploying a build to other servers that can connect to the same offsite storage location. For information on how to set up offsite storage, see the Offsite Backups page.

Publishing via FTP or SFTP

OttoFMS 4.11.0 introduces the ability to publish builds via FTP or SFTP. This is useful if you want to publish your build to a web server or CDN that is FTP or SFTP enabled. If you want to host Public Builds off your FileMaker Server, this is the way to go.