Skip to content

About

Téléservice de dépôt des déclarations de conformité au RGAA des services publics numériques.

Resources

Stars

1 star

Watchers

1 watching

Forks

Repository files navigation

Téléservice Conformité

Monorepo of the French digital accessibility compliance service: apps/teleservice, the declaration application built with Next.js, Payload CMS, and tRPC, and apps/site, the public RGAA 5 site (Next.js App Router exported as static HTML). The RGAA 5 sources live in rgaa/content/ and are read and checked by packages/content (see rgaa/README.md and docs/rgaa5-integration.md).

Layout

apps/teleservice/   the compliance application (Next.js, Payload, Postgres), port 3000
apps/site/          the public RGAA 5 site (Next.js App Router, static export), port 3001
packages/content/   @rgaa/content: reads and validates rgaa/content/, builds the published model
rgaa/               RGAA 5 sources (content/) and generated data (data/), see rgaa/README.md
docs/               ADRs, agent guides, RGAA 5 integration decisions

The workspace is managed by pnpm and orchestrated by Turborepo.

Getting Started

Prerequisites

  • Node.js 22
  • pnpm, through Node's Corepack (corepack enable) — the version is pinned in package.json

Installation

  1. Install dependencies (from the repo root):
pnpm install
  1. Configure environment variables for each application:
cp apps/teleservice/.env.example apps/teleservice/.env
cp apps/site/.env.example apps/site/.env
  1. Start the database and the mail catcher:
docker compose up -d
  1. Start the development server:
pnpm dev
  1. Visit http://localhost:3000 for the teleservice and http://localhost:3001 for the RGAA 5 site.

Everyday commands

All run from the repo root.

Command What it does
pnpm dev dev server of every app
pnpm build production build of every package
pnpm test vitest in every package
pnpm typecheck tsc --noEmit in every package
pnpm run check / pnpm check:write oxlint + oxfmt, check or fix, repo-wide
pnpm --filter teleservice <script> one app's own script (payload, seed:dev, …)

Deployment (Clever Cloud)

Teleservice

The teleservice deploys from the repository root on a Node.js application. Clever Cloud detects pnpm-lock.yaml and reads the pnpm version from the packageManager field, and installs the whole workspace during its build phase.

Variable Value
NODE_ENV production
CC_NODE_BUILD_TOOL pnpm (or unset: the lockfile is detected)
CC_NODE_DEV_DEPENDENCIES install: the build needs dev dependencies (TypeScript, @types/*)
CC_POST_BUILD_HOOK pnpm --filter teleservice payload generate:types && pnpm --filter teleservice build && pnpm --filter teleservice payload migrate
CC_RUN_COMMAND pnpm start:teleservice

packageManager pins pnpm 11: Clever Cloud implements CC_NODE_DEV_DEPENDENCIES=install as pnpm install --prod false, a spelling pnpm 12's new argument parser no longer accepts (it reads false as a package name). Move to pnpm 12 once the buildpack emits --prod=false. The hook builds the teleservice only: pnpm build at the root would also build the RGAA 5 site, which this application does not serve. The root manifest has no start script, one start:<app> script per application instead. The Payload CLI runs through the app's payload script so that it resolves the app's config and migrations.

RGAA 5 site

pnpm --filter site build writes a fully static export to apps/site/out/; pnpm start:site serves it locally. It is meant to be served by a Clever Cloud static application (CC_WEBROOT=/apps/site/out, build through CC_POST_BUILD_HOOK=pnpm --filter site build). Not deployed yet.

About

Téléservice de dépôt des déclarations de conformité au RGAA des services publics numériques.

Resources

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages