All projects

Projects Generator

From idea to a live app in minutes

Role
Personal project: back end, front end and infrastructure automation
Status
In production

The problem

Starting a new project meant hours repeating the same setup: authentication, Docker, CI, database, domain, HTTPS and deployment.

What I built

  • Creates the repository from templates (Spring Boot API and Angular web) that already include login, tests, a Dockerfile and CI.
  • On the platform: creates the database and user, seals the secrets, registers the app in the catalog and follows it until it is live.
  • Optional Kafka integration (producer and consumer topics) and topic management from the same screen.
  • Standalone mode: generates the project with Docker Compose, Caddy (HTTPS), backup scripts and a deployment guide to run on any VPS, branded for the client.
  • App removal with a database backup.

Architecture

  1. Generator UIname, type, database, Kafka
  2. Generator APISpring Boot
  3. GitHubrepository created from the template
  4. GitOps repositorycatalog and sealed secrets
  5. Argo CDdeploys to the cluster
  6. <product>.systemsgf.xyzlive with HTTPS

Technical decisions

Real templates instead of text generation

The generator starts from template repositories that compile and have tests, and only swaps names and settings.

Infrastructure always through commits

Every platform change is a commit to the GitOps repository, re-read on each attempt to avoid conflicts.

Least privilege

The generator reads cluster state with a read-only Role; Argo CD is the one applying changes.

Technologies

  • Java 21
  • Spring Boot 4
  • Angular 22
  • GitHub API
  • Argo CD
  • Sealed Secrets
  • Kafka
  • Docker Compose
  • Caddy

Outcome

GGoals, this portfolio and the platform’s test apps were created by the generator, with login, CI and deployment ready from day one.