Deploy with Digital Ocean Apps
We will deploy our application to Digital Ocean Apps. This is by far the easiest (but most costly) approach.
Using the DigitalOcean App Deployment, we can simply connect our repository to DigitalOcean, and it will handle any changes and deploy them.
However, as DigitalOcean Apps do not yet natively support Deno, nor allow us easy access to the server, we need to ensure the migration is run on deployment before the application is started.
In your DigitalOcean account, start by selecting
Apps from the
We'll now walk through the options you will be presented with to set up the service, starting with selecting the source repository.
Digital Ocean Apps deployment will scan your repository and assume the app type depending on the files present, e.g. if a
package.jsonfile is in the root, it will assume that it is a Node app, while with a
Dockerfile, it will assume that it should build the Docker image.
Thanks to the
Dockerfile in our root directory, DigitalOcean automatically
selects the app type of a Docker image, remember to check the box for
The next set of options are not that important as we will be changing them later, but for now, make sure that the Type is set to "Web Services".
Now is a good time as any to add the database. You can either leave the name to
the default or give it a custom name. I will name it
quacker as it doesn't
really matter as you will see further down.