Pontoporeia b12ae73e91 tests: fix SecurityTest fatal TypeError — update searchTheses call to use array params
SecurityTest::Test1 was calling $db->searchTheses($string) with a plain
string, but searchTheses() was refactored to require array $params when
the tag M2M work landed.  This caused an immediate PHP fatal TypeError
before any SQL ever ran, killing the entire Security test suite with
exit code 255 and masking all three tests.

Fix: pass each malicious payload via ['query' => $string] which is the
correct API and properly exercises the parameterised query path through
validateSearchParams() + buildSearchConditions().  Added a clarifying
comment explaining why the array form is required.

All 4 test suites now pass:
  - Database (Unit):   7/7
  - Rate Limit (Unit): 5/5
  - Search (Integration): 6/6
  - Security:          3/3
2026-03-26 18:54:20 +01:00
2026-03-11 12:39:18 +01:00
2026-03-11 12:39:18 +01:00

posterg

Répertoire des travaux de fin d'études de l'ERG (École de Recherche Graphique).

Requirements

  • PHP 8.4
  • SQLite3 (php8.4-sqlite3)
  • nginx (production)

Project structure

posterg/
├── public/          # DocumentRoot — web-accessible only
│   ├── admin/       # Admin panel (session-authenticated)
│   ├── assets/      # CSS, fonts, icons
│   ├── media.php    # Controlled file serving (covers, PDFs)
│   └── *.php        # Public pages (index, search, tfe, apropos)
├── src/             # PHP classes (not web-accessible)
│   ├── AdminAuth.php
│   ├── Database.php
│   ├── RateLimit.php
│   └── config.php
├── templates/       # Shared PHP template partials
├── config/          # Bootstrap and credentials (not web-accessible)
├── storage/         # Database and uploaded files (not web-accessible)
│   ├── schema.sql
│   ├── test.db
│   └── fixtures/
├── tests/
├── scripts/         # Dev and server management scripts
│   ├── setup-dev.sh
│   ├── deploy-server.sh      # Run on server with sudo to apply nginx config
│   └── manage-admin-users.sh # Run on server with sudo to manage htpasswd
└── nginx/           # nginx config and reference files
    └── posterg.conf

Uploaded files (PDFs, covers) live in storage/ — outside the webroot — and are served exclusively through public/media.php, which validates paths and MIME types.

Development

just setup   # first-time: installs dev dependencies
just serve   # http://localhost:8000  (public) and /admin/
just test    # run test suite

Admin credentials in development are set via config/admin_credentials.php (see config/admin_credentials.example.php).

Deployment

Files are pushed to the server with rsync — there is no repo on the remote.

just deploy     # rsync app files → posterg:/var/www/posterg/
just deploy-db  # push local test.db → remote (only if remote DB is absent)

deploy-db refuses to run if a database already exists on the server, to avoid accidental overwrites of production data.

First-time server setup

ssh posterg
sudo mkdir -p /var/www/posterg
sudo chown www-data:posterg /var/www/posterg
sudo chmod 775 /var/www/posterg
exit

Then deploy once, copy nginx config, and apply:

just deploy
rsync -v nginx/posterg.conf posterg:/tmp/posterg.conf
ssh posterg "sudo bash /var/www/posterg/scripts/deploy-server.sh"
ssh posterg "sudo systemctl reload nginx"

Admin users (htpasswd)

ssh posterg "sudo bash /var/www/posterg/scripts/manage-admin-users.sh"

Security notes

  • Admin panel protected by nginx auth_basic + PHP session (AdminAuth)
  • Uploads stored outside webroot, served via controlled media.php
  • Rate limiting on public search (src/RateLimit.php)
  • See docs/TODO.SECURITY.md for outstanding items
Description
Site permettant de consulter la collection de TFE de l'erg
Readme 74 MiB
Languages
PHP 80.5%
CSS 14.9%
Shell 2.8%
JavaScript 1.3%
Just 0.5%