sapling / skeleton

dev-main 2026-10-23 10:00 UTC

Requires

• php: >=8.4
• sapling/core: dev-main

Requires (Dev)

• pestphp/pest: ^5.3

0BSD

Published on Packagist.org on 2026-10-23 10:01 UTC

README

A blank Sapling app.

composer create-project sapling/skeleton:dev-main my-app
cd my-app
composer serve

/ping answers pong, and composer test checks it. Add your actions and commands to app/ and their tests to tests/. Read the Sapling guides to go further.

Docker

The Dockerfile runs the app on FrankenPHP. Its settings come from a .env on the server with production values. Don't copy the one you work with, since its APP_ENV=dev turns on debug mode:

APP_ENV=production
APP_KEY=...

Write each line as plain KEY=value, since Docker keeps quotes and # comments as part of the value. Keep the file out of git and back it up, because without its APP_KEY nothing encrypted can be read again.

Build the image, then run it with that file and a volume for the database at /data:

docker build -t my-app .
docker run -d -p 80:80 --env-file .env -v my-app-data:/data --name my-app my-app
docker exec my-app php bin/console migrations:run

The container runs as a user without root, and its health check calls /ping, so keep that route. Run one container per volume, since two can't share a SQLite file safely. Behind a host's proxy, such as Fly or Render, add 'trusted_proxies' => ['*'] to config.php. To serve HTTPS yourself, set SERVER_NAME to your domain.