Recent content on Ordinary Blog
One major advantage of Ordinary’s architecture is that it makes it possible to derive insights about behavior and performance without a ton of additional time spent configuring and tuning instrumentation yourself. 
 When you use Ordinary, the facilities for request/response logging, as well as inter-service communication are wired up immediately for templates, actions, proxies,…
With v0.8 , we’ve added initial support for Ordinary Middleware. For this first release we’ve kept narrowly focused on validation operations that can be delegated to external services via HTTP request. 
 Example Case 
 One tool that we’re excited about and is well-aligned with our #NoAI agenda is Iocaine —a service which runs as a separate daemon that filters out requests…
Starting with version 0.7.0 we’re adding support for reverse proxies on Ordinary. Configurable as path or domain , reverse proxying within ordinaryd can be used to unify a group of services under a single app domain, or automate TLS termination, request logging, and compression for an origin server with minimal headache. 
 Path-based 
 The path-based configuration is primarily useful…
Having spent a bit of time now working with Ordinary to run my personal blog , I wanted to set up a more formal facility for posting about the framework itself. 
 Ordinary has always been designed with the idea that it should be just as (or moreso) straightforward to run your own space on the web as it is to set up an ActivityPub account – so, for that reason, I picked to build its blog…