Skip to content
Edson Francisco
  • Reliability, DevOps & legacy

Perpi Dashboard

Containerisation and self-hosted Coolify deployment for a team's Angular/Ionic dashboard.

Period
2025
Status
In development
Role
DevOps and deployment documentation

Problem

The team's dashboard for products, purchases and members ran in development mode, but there was no documented way to build and publish it.

Solution

The application is the team's; Edson's part was the deployment. He wrote a multi-stage Dockerfile, the Nixpacks configuration for Coolify, a deployment guide covering both paths, a checklist and a full README.

Technical decisions

  1. 01

    Final image with static files only

    The build runs in a Node image and the final image only serves the www folder, with a health check. The image stays small and does not ship the toolchain.

  2. 02

    SPA fallback without nginx

    http-server with --proxy returns index.html for any route, so deep links work without configuring a separate web server.

  3. 03

    Two documented deployment paths

    Nixpacks as the recommended path on Coolify and Docker as the alternative, so the team is not tied to a single way of publishing.

Images

No publishable screens: the system needs real data to run or is no longer online.

Technologies

  • Docker
  • Coolify
  • Angular
  • Ionic
  • Supabase

Verifiable results

lines of infrastructure and deployment docs
+1 082