Software Engineering Intern

Jul - Oct 2026 · Pau

ASR Nettoyage

I built the ERP used by ASR Nettoyage in Pau, on the open-source Twenty CRM: React and TypeScript front end, NestJS and GraphQL back end, PostgreSQL and Redis. I added the planning, HR, quote and revenue screens, imported data from the company's Wo Nett (HFSQL) software, and set up the CI/CD that builds the application image on every push and deploys it on the company's server. The ERP has been in production since August 2026.

01

What I built

  • ERP screensSeventeen React/TypeScript screens: daily cockpit, weekly planning with absences and replacements, commercial pipeline, quote editor with PDF output, revenue dashboard and contract alerts.
  • Data modelHR and CRM objects: employees, sites, assignments, shifts, absences, quotes, contracts and field visits.
  • Wo Nett synchronisationA scheduled task picks up the Wo Nett exports every 30 minutes and imports them idempotently, keyed on Wo Nett identifiers. Quotes go back in Wo Nett's import format.
  • CI/CDEach push to main builds the application's Docker image in GitHub Actions and publishes it with a commit tag. The server pulls it and restarts the stack: Caddy for HTTPS, application and worker, PostgreSQL and Redis, with health checks.
  • OperationsNightly database backups with retention, a sync log recording every import decision, and a read-only production survey.
02

Delivery and data flow

ASR ERP: code delivery and data synchronisationA push to main triggers a GitHub Actions build of the application's Docker image, published to a registry with a commit tag; the company server pulls it and restarts the stack, Caddy for HTTPS, the application and its worker, PostgreSQL and Redis, with health checks. Separately, a scheduled task imports the Wo Nett table exports every 30 minutes, keyed on Wo Nett identifiers, and quotes are exported back in Wo Nett's import format.keyed on Wo Nett IDsquotes back in Wo Nett import formatPush to mainERP repositoryImage buildGitHub Actions, DockerRegistrytagged by commitCompany servermanual pull, restartERPCaddy HTTPSapp and workerPostgreSQLRedismy screens anddata modelWo NettHFSQL, hosted desktopTable exportsspreadsheet filesSync taskevery 30 min, idempotent
  • Data
  • Command
  • My work

FIG. 01Code and data paths. The image is built off the server, which has too little memory for the front-end build. Direct read access to HFSQL is not available on the hosted installation, so synchronisation runs on exports.
03

Status

Online since 11 August 2026 and used in production since the end of August. Company code, operational data and figures stay internal.