The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Outingo – Automated CI/CD Deployment with GitHub Actions
Implemented an automated CI/CD pipeline for the Outingo application using GitHub Actions. Configured the workflow to securely connect to an AWS EC2 server via SSH, pull the latest code, update Docker-based services, and deploy application changes automatically. Managed GitHub Actions secrets and Linux-based deployment environments while troubleshooting deployment and container-related issues.
Skills: GitHub Actions, CI/CD, Docker
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Onboarding flow for midcode.app
For a multi-tenant backend, I keep tenant configuration out of the Docker build whenever the tenants run the same code.
One application image. Tenant configuration at runtime. Separate deployment credentials and data boundaries.
In GitHub Actions, I copy package manifests before application source, use npm ci, and reuse BuildKit cache. A source edit shouldn’t force a fresh dependency installation.
The multi-stage Dockerfile keeps compilers and build tools out of the runtime image.
I also tag images with the commit SHA and promote the same artifact through staging and production.
Build speed matters, but so does knowing that the image tested in staging is the image being deployed. Database migrations get an explicit step, with compatibility checked before rollout.
