08 Deployment & DevOps

• Learning objectives for the week

Topics covered in this week are:

Deploying Javalin applications on Docker in the Cloud using:

• Docker
• Continuous Integration & Deployment
• GitHub Actions
• Docker Hub
• Watchtower
• Ubuntu VM on Digital Ocean
• Caddy Server
• Domains, SSL Certificates, and HTTPS

Feedback on portfolio project.

For the rest of the day: Prepare for the week. Watch the videos and read the articles.

Watch this video:

• CI / CD in 5 minutes
• Docker file (from 49:09 - 58:30)

Skim through these articles (orient yourself with the content, you don’t need to read everything in detail):

• Continuous integration vs delivery vs deployment

• Dockerfile reference

• Docker Compose reference

• Github Actions (first page)

1. It would be good if you have a domain name ready. It takes a little while to get a domain activated and have the dns handling transfered to Digital Ocean. If you don’t have a domain name yet, please follow this tutorial.

2. Also, sign up on Digital Ocean if you haven’t done that already. Here is a tutorial.

3. Make sure you have a Droplet running on Digital Ocean. Here is a tutorial.

• CI/CD slides

• Github Actions and Docker Hub Tutorial

Today we will work on deploying your portfolio project on a Digital Ocean Droplet. We will use Docker, Watch Tower, and Caddy Server to deploy the web api.

The goal is to have a running web api on a Digital Ocean Droplet with a domain name and SSL certificate. The web api should be accessible through the domain name and should be updated automatically when a new version is pushed to the Docker Hub.

1. First off a premiere of the new event Architecture Bingo 2026.
2. We will continue working with deployment of your portfolio project - and make sure everything is okay.
3. There will be time to get help with your portfolio project.

Portfolio project deployment and finalization. Make sure your portfolio project is deployed and running on a Digital Ocean Droplet with a domain name and SSL certificate. The web api should be accessible through the domain name and should be updated automatically when a new version is pushed to the Docker Hub.

You don’t need to have your backend finished by now - but when the deployment pipeline is set up, it will be easy to deploy the backend when it is finished.