CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/devops-essentials

DevOps essentials — Dockerfile best practices, CI/CD patterns, deployment configuration, and container security

89

1.21x
Quality

87%

Does it follow best practices?

Impact

100%

1.21x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-1/

Full-Stack React + Express App with Docker Compose

Problem/Feature Description

A team is building a full-stack application with a React frontend and an Express/Node.js (TypeScript) backend API. They need to containerize both services and set up docker-compose for local development and production deployment.

Frontend (React):

  • Built with Vite, outputs static files to dist/
  • In production, served by nginx
  • Runs on port 80

Backend (Express API):

  • TypeScript, compiles to dist/
  • Connects to a PostgreSQL database
  • Runs on port 3000
  • Has a /health endpoint

Database:

  • PostgreSQL, needs persistent storage

The project structure is:

/frontend/  — React app (has its own package.json)
/backend/   — Express API (has its own package.json)
/docker-compose.yml

Output Specification

Produce:

  • output/frontend/Dockerfile — Dockerfile for the React frontend
  • output/backend/Dockerfile — Dockerfile for the Express backend
  • output/docker-compose.yml — Docker Compose configuration for all services
  • output/.dockerignore — Docker ignore file (can be shared or per-service)
  • Any other files needed for a complete setup (nginx config, etc.)

All files should be production-ready. No placeholders or TODO comments.

evals

scenario-1

criteria.json

task.md

tile.json