Search by

jonbaldie / functions

jonbaldie

There is no license information available for the latest version (v3.0.1) of this package.

A skeleton PHP project based on the principles of functional programming and pure functions.

Package info

github.com/jonbaldie/functions

pkg:composer/jonbaldie/functions

Statistics

Installs: 36

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 4

v3.0.1 2026-11-05 10:35 UTC

README

PHP Functional Programming Skeleton Project

CI

Functions is a PHP skeleton project built upon a foundation of pure functions. It's a fun personal project of mine but it is unit tested and stable, if you'd like to give it a go.

Just run this to get started:

composer create-project jonbaldie/functions my-project && cd my-project

Then to generate your front-end assets:

yarn install && yarn encore dev

Protect the encryption key

Composer creates .key with owner-only permissions. The project directory must support hard links so the generator can publish a complete key without overwriting an existing one. Keep the file outside any public web directory. If the web server runs as another user, give that account read access through a dedicated group or an access control list. For example, add the runtime account to a dedicated group, set that group on .key, and use mode 0640. Restrict access to the project directory as well.

Existing keys and their permissions are not changed. Review keys generated by earlier versions for exposure. If a key may have been exposed, plan a rotation and re-encrypt protected values before retiring the old key.

Start a local PHP server:

cd public && php -S localhost:3000 index.php

Open http://localhost:3000 and you should see "It works!"

See the skeleton exploratory pass and the 2026-11-06 exploratory pass for setup, routing, asset, and key observations.

expose_env() gives $_ENV values precedence and skips process lookups for those keys. It still looks up each other process key separately, so a large environment with few $_ENV overrides can take quadratic time on glibc. env() reads one key without rebuilding the full merged snapshot.

Wait, what's a "pure function"?

Pure functions map variables from an input and produce an output, with no observable side-effects. They're easily testable, can be moved anywhere, and used in any context with no unexpected effects. This concept comes from functional programming languages like Clojure, Scala, or Haskell.

Functional programming - an approach that holds pure functions at its core - is growing in popularity. Developers are challenging the utility of traditional methods that run the risk of producing code that's difficult to debug. What's simpler than a pure function that does nothing more than map an input to an output?