Coder Legion - Recent posts tagged digitalocean

Effortless Web App Deployments with GitHub Actions

Sat, 13 Dec 2025 16:33:23 +0000

Automating Production Deployments on DigitalOcean

Deploying web applications manually gets painful fast — especially once your project grows.

For azan.lk, a Laravel + React application running on a hardened DigitalOcean droplet, I moved from manual SSH-based deployments to a fully automated CI/CD pipeline using GitHub Actions.
Every push to main now builds, deploys, and optimizes the app automatically — safely and consistently.

This article gives you a practical, production-ready overview of how to automate deployments without overengineering.

⚙️ What This Covers

This guide focuses on real-world CI/CD for VPS-based deployments, not platform-locked solutions.

You’ll learn how to:

Automate deployments using GitHub Actions
Build Laravel & React outside the server
Deploy via SSH securely
Run database migrations and optimizations remotely
Keep your DigitalOcean droplet lean and stable
Eliminate repetitive SSH workflows

Perfect for portfolios, SaaS apps, client projects, or APIs running on a VPS.

Prerequisites (Important)

Before adding automation, your server must already be production-ready.

Make sure you’ve completed these first:

Server Hardening
- Non-root user
- SSH keys
- Firewall & Fail2Ban
  Fortify Your DigitalOcean Droplet: A Step-by-Step Security Guide for Ubuntu 24.04
HTTPS & SSL
- Nginx
- Let’s Encrypt
- Auto-renewal
  Unlock Free HTTPS with Let’s Encrypt SSL
Manual Deployment Setup
- Laravel + PHP-FPM
- Nginx
- MySQL
- Node & Vite
  Streamlined App Deployment on Ubuntu 24.04

Once those are done, CI/CD becomes the final layer — not a replacement.

The Problem with Traditional Deployments

A typical manual deployment looks like this:

SSH into the server
Pull latest code
Run Composer
Run NPM builds
Fix permissions
Run migrations
Hope nothing breaks

On small VPS instances, Composer and NPM can consume memory, slow the server, or even crash builds.

And doing this repeatedly?
That’s technical debt waiting to happen.

What You’ll Accomplish with CI/CD

By the end of this setup, you’ll have:

Automatic deployments on every push to main
Builds handled by GitHub, not your VPS
Secure SSH-based file sync
Zero manual server logins for deploys
Reliable, repeatable production releases

Push code → GitHub Actions runs → App goes live

Why This Approach Works

This setup is optimized for developers who:

Use VPS hosting instead of managed platforms
Want full control over infrastructure
Care about performance and stability
Prefer simple, understandable pipelines

No Kubernetes.
No overcomplicated workflows.
Just clean automation that works.

Read the Full Step-by-Step Guide

The full article includes:

Complete deploy.yml workflow
GitHub Secrets setup
SSH key best practices
Common CI/CD pitfalls (and how to avoid them)
Production-safe Artisan commands

Effortless Web App Deployments: Mastering GitHub Actions with DigitalOcean

✨ Final Thoughts

CI/CD isn’t about complexity — it’s about removing friction.

Once this pipeline is in place:

Deployments become boring (that’s good)
Servers stay fast
Mistakes drop dramatically
Your workflow scales with your project

Pair this guide with Streamlined App Deployment on Ubuntu 24.04, and your readers get a complete journey:

Manual setup → hardened server → automated production deployments

Streamlined Production Deployment on Ubuntu 24.04

Wed, 03 Dec 2025 14:21:31 +0000

Deploying a full-stack application for production doesn’t have to be complicated — especially if you follow a structured setup. For azan.lk, a Laravel + React project backed by MySQL, I built a fully optimized, secure deploymenton Ubuntu 24.04, running on a DigitalOcean Droplet.

This post is a quick overview of what the major components you’ll handle.

⚙️ What This Covers

This deployment walkthrough is designed for modern full-stack apps and covers the full stack you’d expect in real production:

Laravel backend (PHP 8.4, FPM, Composer)
React frontend (bundled via Vite)
MySQL database (hardened & configured)
Nginx production server
Node.js + NPM via NVM
Git + SSH for secure deployments
Environment setup, permissions, and optimizations

If you’re deploying a portfolio, client project, SaaS, or API backend, this setup gives you a fast, stable, security-conscious structure.

Before Deployment: Essential Prerequisites

Make sure your droplet is secure and ready for production.
I recommend completing these two guides first:

1. Server Hardening (Must Do Before Anything)

Fortify Your DigitalOcean Droplet: A Step-by-Step Security Guide for Ubuntu 24.04
A complete walkthrough covering non-root users, SSH keys, firewall, Fail2Ban, and more.

2. Enable HTTPS (Required for Live Apps)

Fortify Your Droplet: Unlock Free HTTPS with Let’s Encrypt SSL
Includes DNS setup, Nginx configs, SSL installation, and auto-renewal.

Once both are done, your droplet is safe to host real traffic — and ready for deployment.

✨ What You’ll Accomplish

Install PHP 8.4 with all required extensions for production
Set up Composer safely using the official installer
Configure MySQL with proper users, permissions, and best practices
Install Node.js via NVM for frontend builds
Set up Git SSH keys for secure repository access
Configure application permissions for Laravel
Build and optimize your frontend assets for production
Set up Nginx with proper routing, headers, and FPM integration
Run database migrations and seeders
Troubleshoot common deployment issues like PHP errors, permissions, or SSH problems

Every step — with commands, configs, and explanations — is included in the full guide on Hashnode.

Read the Full, Detailed Guide

The complete command-by-command walkthrough — including explanations, and best practices — is available on my blog.

Read the full article here:
Streamlined App Deployment: Launch Your First Web App on Ubuntu 24.04 with DigitalOcean

The post includes every command, config file, and optimization used in the real-world deployment of azan.lk.

Why This Guide Matters

Most deployment tutorials are outdated, incomplete, or skip critical production details.
This guide focuses on:

Security (SSL, firewall, SSH hardening)
Performance (PHP-FPM tuning, Vite builds)
Stability (MySQL, permissions, proper Nginx configs)
Developer workflow (Git SSH, easy updates, reliable builds)

Ideal for developers deploying real-world projects into production.

Final Thoughts

A reliable deployment is more than just “upload code and run”:
it’s a combination of security, performance, and correct configuration.

Secure Your DigitalOcean Droplet with Free HTTPS (Let’s Encrypt + Certbot)

Wed, 03 Dec 2025 07:59:56 +0000

Once your droplet is hardened with a non-root user, SSH hardening, and a firewall, the next upgrade you must add is HTTPS.

Without HTTPS, your login pages, API requests, and user data travel in plain text — easy for attackers to sniff or intercept. With HTTPS enabled, you get encrypted traffic, improved trust, and that familiar browser padlock that tells users their connection is safe.

This post is a quick overview of what the HTTPS setup includes.

Start Here: Droplet Hardening Guide (Before HTTPS)

Before diving into HTTPS, make sure you’ve completed the hardening steps covered in my first guide:
Fortify Your DigitalOcean Droplet: A Step-by-Step Security Guide for Ubuntu 24.04

✨ What You’ll Accomplish

Connect your domain to the droplet
Configure Nginx properly for production
Install Certbot + Let’s Encrypt
Enable secure HTTPS with automatic renewal
Redirect all HTTP traffic to HTTPS
Validate the setup with a clean, secure padlock indicator

Every step — with the exact commands — is included in the full guide.

Why HTTPS Matters

Protects login and API endpoints
Encrypts form data, cookies, and tokens
Immediately boosts user trust
Required by OAuth providers, Stripe, Clerk, Firebase, and more
Works seamlessly with any backend (Laravel, Node.js, Go, Spring Boot, etc.)

Whether you're deploying a portfolio, SaaS app, REST API, or production service, HTTPS is non-negotiable.

Read the Full, Detailed Guide

The complete command-by-command walkthrough — including explanations, and best practices — is available on my blog.

Read the full article here:
Fortify Your Droplet: Unlock Free HTTPS with Let’s Encrypt SSL

(Every command and configuration is included — nothing hidden.)

After You Follow the Guide, Your Droplet Will Be:

✅ Fully encrypted with HTTPS
✅ Protected from MITM attacks
✅ Auto-renewing SSL forever
✅ Ready for real production workloads
✅ Safe for sessions, passwords, and API traffic

Fortify Your DigitalOcean Droplet: A Step-by-Step Security Guide for Ubuntu 24.04

Tue, 02 Dec 2025 18:54:08 +0000

Launching a production app isn’t just about clean code or beautiful UI — it’s about making sure the server behind it is hardened, protected, and ready for real-world traffic. A poorly configured droplet can be compromised in minutes, and the cost of recovery is far greater than the cost of prevention.

To help fellow developers avoid those risks, I documented the exact hardening process I used for azan.lk, a Sri Lanka–focused Islamic portal. These steps apply to any project — personal, client-based, or fully commercial.

What You’ll Achieve

By the end of this guide, you’ll have a droplet that’s:

Hardened and production-ready
Protected with SSH key–only access
Locked down with root login disabled
Secured with a properly configured UFW firewall
Reinforced with optional tools like Fail2Ban and unattended security updates

These are foundational steps I recommend before deploying any backend, frontend, Docker service, or microservice.

What This Guide Covers

1. Organizing Your DigitalOcean Project

Set up a clean DO workspace so your droplets, DNS records, metrics, and backups stay organized.

2. Building a Secure Droplet

Recommended specs for most apps:

Ubuntu 24.04 LTS
2GB RAM / 2 CPU
60GB SSD
Singapore or Bangalore for low latency to Sri Lanka

3. SSH & User Configuration

Create a non-root sudo user
Add SSH key authentication
Disable password login
Disable root login for safety

4. Hardening Essentials

Strengthen your droplet with:

Strict SSH configuration
UFW firewall
Fail2Ban jail protection

5. Developer Quality-of-Life Enhancements

Set up a local SSH config so logging into your droplet becomes instant and password-free.

✨ Why I Wrote This

When I first started deploying production systems, server security felt like something for “later.”
Then I learned how vulnerable a fresh droplet is out of the box — and how quickly it can be scanned, probed, or exploited.

Now I document my setup processes so other developers can deploy with confidence and avoid the pitfalls I learned the hard way.

This article is perfect if you’re deploying:

Laravel, Node.js, or Go applications
React, Vue, or Next.js frontends
Docker containers / microservices
APIs or production websites

Read the Full, Detailed Guide

The complete command-by-command walkthrough — including explanations, and best practices — is available on my blog.

Read the full article here:
Fortify Your DigitalOcean Droplet: A Step-by-Step Security Guide for Ubuntu 24.04

(Every command and configuration is included — nothing hidden.)

Final Thoughts

Security isn’t a one-time task — it’s an ongoing practice.
But this guide gives you a solid, battle-tested foundation for any production environment, whether you’re hosting a small personal app or a full-scale platform.