The current image used for 1-click deployment on DigitalOcean does not contain the source or binary of SMP Server - it downloads the compiled binary of the latest release (rather than a particular release) from GitHub.

The upside is that the new image does not have to be created and approved by DigitalOcean every time when the new release is created.

The downside is that while the release is being prepared in CI, when the release object is already created in GitHub but the server binary is not attached yet, the attempt to install the server would fail - it can last anything from several to 20 minutes, depending on whether the cached dependencies were used or everything was recompiled. Currently, when there is a small number of users, it is not a big problem, but we should consider some possible solutions in the future. Linode StackScript has the same issue.

How to build an image

Create an API token in vendor account in DigitalOcean.
Install packer downloading binary or with brew (on Mac):

brew tap hashicorp/tap
brew install hashicorp/tap/packer

Run packer build in the smp-server-digitalocean-droplet repository:

cd ./scripts/smp-server-digitalocean-droplet
DIGITALOCEAN_TOKEN=$YOUR_TOKEN packer build -on-error=ask -color=false ./marketplace-image.json