Public builds are builds that are hosted on a webserver and are accessible to anyone. They are used to distribute your app to your users. How widely you distribute your app is up to you. You can distribute it to a small group of testers, or you can distribute it to the entire world.
OttoDeploy's build interface walks you through the process of choosing the files to include in the build, and whether to clone or copy them, and how to run a script before the build to prepare your files.
Kick off the build with OttoDeploy. OttoFMS will process the files according to your configuration and create a zip archive of the build.
Use OttoDeploy to download the build. Unzip the archive and extract the manifest.json file. Leave the archive intact. You will need both the manifest.json file and the archive to distribute your build.
Upload the build to a webserver. You can use any webserver you like. You can use a service like AWS S3, or you can use your own webserver. The only requirement is that the files are accessible via a url. See the example file system below for the best practices for hosting your public builds.
Place the zip archive and the manifest.json file next to each other on a webserver. You would use a structure like this to host your public builds.
If the url to your web-accessible folder is
https://myserver.com/public-builds, then the url to the first build would be
OttoDeploy and SimpleQ (opens in a new tab) are both available as public builds.