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
Inception is a containerized web infrastructure project built with Docker and Docker Compose. I configured Nginx with TLS, WordPress with PHP-FPM, and MariaDB as isolated services, including persistent storage, secure networking, environment configuration, and automated service orchestration. It demonstrates my DevOps, Linux, containerization, and infrastructure engineering skills.
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
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
Designed and built Startups Coimbra, the website and community platform for an open startup community in Coimbra, Portugal — a React + TanStack Start SSR app with a custom dark, technical design system.
It includes a server-side waitlist that feeds signups straight into Attio CRM with Startup/Mentor segmentation, plus full Portuguese content and technical SEO (per-route metadata, canonicals, OG cards, sitemap).
Live at startupscoimbra.pt.
Title: AI Resume Analyzer | MERN & AWS Smart Resume Evaluation Platform
Technologies Used: React.js, Node.js, Express.js, MongoDB, AWS S3, REST API, JWT Authentication, Responsive Web Design, AI Integration
About:
Designed and developed AI Resume Analyzer, a full-stack MERN and AWS-powered web application created to help users improve ATS compatibility, resume quality, and job readiness through intelligent AI-driven analysis. The platform supports secure resume uploads, user authentication, real-time resume evaluation, structured skill extraction, keyword analysis, and responsive dashboard interfaces for a seamless user experience across desktop and mobile devices. Built using React.js, Node.js, Express.js, MongoDB, AWS S3, and REST APIs, the project demonstrates expertise in full-stack development, AI integration, cloud deployment, authentication systems, scalable application architecture, and building production-ready web solutions with modern UI/UX principles.
Introduction
In the first method, we coupled all of the services into one stack using a single Docker Compose file. The network between all services was created automatically, and we didn't have to start them up individually — which removes the risk of a race condition if service startup isn't handled properly.
If you're running a single app, that's genuinely the recommended way to set up Directus on a Coolify-managed VPS. Going in, I assumed there were several good reasons to split the services apart instead — more control over backups, monitoring, restarts, that kind of thing. So before recommending decoupling, I actually tested each of those assumptions on a live Coolify instance.
Most of them turned out to be wrong.
Myth 1: Restarting Directus Restarts the Whole Stack
I expected that restarting Directus inside the bundled Compose file would restart Redis and Postgres along with it. It doesn't. Coolify lets you restart each service in the stack independently — Directus, Database, and Cache each get their own Restart button, right there in the same view. No decoupling needed for this one.
Myth 2: You Need a Separate Database Resource for S3 Backups
Same story. Even with Postgres bundled inside the Directus Compose file, Coolify still gives it its own dedicated Backups option, S3 included. This isn't a separate-resource-only feature.
Myth 3: Scheduled Tasks Require Separate Services
Also not true. Coolify exposes a Scheduled Tasks tab per service, even inside a single bundled stack — complete with a Container name dropdown letting you target the cron job at just the database, or just Directus, without splitting anything apart.
What Actually Holds Up
Two things survived testing.
First: metrics. This one's confirmed directly in Coolify's own documentation — CPU and memory metrics collection is explicitly not available for Docker Compose–based deployments. If you want to see per-container resource usage through Coolify's built-in monitoring, the service needs to be created as its own standalone resource, not bundled inside a Compose file. This is a real, documented limitation of the bundled approach.
Second: sharing a database across multiple apps. This one isn't a Coolify feature at all — it's just how Docker networking works. A database defined inside one app's Compose file lives on that stack's own private network by default. A second, completely separate application can't reach it without deliberately bridging the two networks. If you've got a desktop app and a mobile app that both need to talk to the same Postgres instance, that database needs to exist as its own standalone resource from the start — it can't stay tucked inside one app's Compose file.
So this really comes down to two reasons to decouple, not five — one a genuine Coolify limitation, the other a structural fact about Docker networking. Let's set both of those up properly.
