As a career pivoter to software, I appreciate when I use a tool, and that tool teaches me about concepts and processes elsewhere.
This time, I learned about project deployment targets through GitLab.
GitLab is an open source version of GitHub, a version-control repository hosting service.
In the process of creating a new blank project (aka a repository) on GitLab, I came across the Project deployment target dropdown, which provided 14 options:
Options (typed verbatim from above) are:
- Kubernetes (GKE, EKS, OpenShift, and so on)
- Managed container runtime (Fargate, Cloud Run, DigitalOcean App)
- Self-managed container runtime (Podman, Docker Swarm, Docker Compose)
- Heroku
- Virtual machine (for example, EC2)
- Mobile app store
- Registry (package or container)
- Infrastructure provider (Terraform, Cloudformation, and so on)
- Serverless backend (Lambda, cloud functions)
- Edge Computing (e.g. Cloudflare Workers)
- Web Development Platform (Netlify, Vercel, Gatsby)
- GitLab Pages
- Other hosting service
- No deployment planned
TL;DR: In one fell swoop, I got descriptions and key examples of deployment targets. This provided much context and unlocked more understanding of the software space.
One day at a time!
Many thanks to the team at GitLab that manages the Create blank project page for consolidating key information.
