potcake 0.5.0

An easy to live with, sensible, and dependable web framework.

To use this package, run the following command in your project's root directory:

Manual usage
Put the following dependency into your project's dependences section:

This package provides sub packages which can be used individually:

potcake:http - Potcake web framework lower-level http components. Includes its vibe.d router.

potcake:web - Potcake web framework higher-level web app components.

potcake:core - Potcake core components used by its subpackages.


An easy to live with, sensible, and dependable web framework built on vibe.d.

Potcake endeavours to:

  • Provide safe and sane defaults
  • Be easy to use how you want or with our opinionated structure
  • Provide useful components that prevent re-inventing the wheel


If you would like to see Potcake in action before reading further, take a look at the examples folder. There you will find demonstration apps for Potcake's features.

Each can be run by cloning this repo, navigating to the example app's base, and running dub run (on macOS MACOSX_DEPLOYMENT_TARGET=12 dub run).



  • Adding multiple route handlers at once and static file serving.
  • Specifying typed URL handlers.
  • Collection of static files from multiple source directories into a single runtime directory using the relevant settings (staticDirectories, rootStaticDirectory, staticRoutePath) and --collectstatic file collection.
  • Use of staticPath for linking to files in the runtime static directory for both inline and DIET templates.



  • Adding route handlers and static file serving.
  • Serving static files from a single directory.

Web Framework

URL Dispatching

Potcake implements Django's URL dispatching system.


import potcake.web;

int main()
    auto webApp = new WebApp;
    .addRoute("/hello/<name>/<int:age>/", &helloUser);

    return webApp.run();

void helloUser(HTTPServerRequest req, HTTPServerResponse res, string name, int age)
    import std.conv : to;
    import vibe.http.status : HTTPStatus;

    res.contentType = "text/html; charset=UTF-8";
<!DOCTYPE html>
<html lang="en">
        Hello, ` ~ name ~ `. You are ` ~ to!string(age) ~ ` years old.

Potcake uses D's flexibility to implement key components of Django's URL dispatching system. The end result is a blending of the ergonomics available in Django with the superior runtime performance of D.

Key components of Django's URL dispatching system are:

  • The URL path expression scheme
  • The ability to extend the path expression scheme through path converters
URL Path Expression Scheme

Django allows the developer to specify values to be captured. This is similar to functionality available in most web frameworks (including vibe.d). Identifiers in angle brackets will be used to extract values from matched paths. Those values are then made available to handlers as strings. After matching the following example path on structure, Django would make name and age string values available to the path's associated handler:


Where things get interesting is Django's URL path expression scheme's path converters.

Path Converters

Captured value specifications can optionally include a path converter. Path converters influence both how their portion of the path is matched when routing, and the type of value passed to an associated handler. Take the following path as an example:


name has no path converter and so would be matched as a string. age on the other hand has the int path converter which matches against integers and passes an integer value to the path's handler. A request to /hello/ash/12/ would match against this path while a request to /hello/ash/twelve/ would not.

Behind the scenes, path converters are objects that:

  • Hold a regex pattern for values they match against
  • Understand how to convert string values to the path converter's return type

Potcake provides Router (used internally by WebApp) which is a vibe.d router that understands Django's URL path expression scheme. Paths are parsed at run-time using built-in or user-provided path converters. Built-in path converters match Django's built-in set. User-specified path converters must first be defined as @safe structs with the following properties:

  • An enum member named regex with a regex character class representing strings to match against within a requested path.
  • A toD function that accepts a const string. The return type can be any desired outside void. This function converts strings to the type produced by the path converter.
  • A toPath function with a parameter of the path converters type that returns a string.
User-defined Path Converter Example
import potcake.web;

@safe struct NoNinesIntConverter
    import std.conv : to;

    enum regex = "[0-8]+"; // Ignores '9'

    int toD(const string value)
        // Overflow handling left out for simplicity.
        return to!int(value);

    string toPath(int value)
        return to!string(value);

int main()
    auto webApp = new WebApp([
        pathConverter("nonines", NoNinesIntConverter())
    .addRoute("/hello/<name>/<nonines:age>/", &helloUser);

    return webApp.run();

void helloUser(HTTPServerRequest req, HTTPServerResponse res, string name, int age) @safe {
    import std.conv : to;
    import vibe.http.status : HTTPStatus;

    res.contentType = "text/html; charset=UTF-8";
<!DOCTYPE html>
<html lang="en">
        Hello, ` ~ name ~ `. You are ` ~ to!string(age) ~ ` years old.

Handlers given to Router via WebApp should at the very least return void and accept an HTTPServerRequest and an HTTPServerResponse. Values extracted from the request's path are saved to HTTPServerRequest.params as strings.

If the parameter signature for a handler is extended with the types returned by its path's path converters then Router will additionally use the path converters' toD functions to pass converted values to the handler.

URL Reversing

Potcake provides a utility function for producing absolute URL paths at potcake.web.reverse. It allows you to define route path specifics in one place while using those paths anywhere in your code base. If you make a change to the central definition, all usages of that definition will be updated.

For example, given the following route definition:

webApp.addRoute("/hello/<name>/<int:age>/", &helloUser, "hello");

you can reverse the definition like so:

reverse("hello", "Potcake", 2);

producing the following URL path:


Static Files

Potcake offers two ways to organize your static files (e.g. images, JavaScript, CSS):

  1. In a central directory
  2. In multiple directories e.g. a directory per package in a larger project.

In each case, static files will by default be served from a local directory named 'static' at the route prefix '/static/'. These settings are controlled by WebAppSettings.rootStaticDirectory and WebAppSettings.staticRoutePath respectively.

Central Directory
  1. Choose one directory in your project for storing all static files.
  2. Set WebAppSettings.rootStaticDirectory to the relative path to your static directory from your compiled executable. You will need to deploy this directory alongside your executable.
  3. Set WebAppSettings.staticRoutePath to the URL to use when referring to static files e.g. "/static/".
  4. Use potcake.web.staticPath to build URLs for static assets.
  5. Call WebApp.serveStaticfiles() before running your app.

See static_files for a demonstration.

Multiple directories
  1. Store your static files in directories throughout your project (in the future we hope to use this to make it possible to build libraries that carry their own static files and templates).
  2. Set WebAppSettings.staticDirectories to the relative paths to your static directories from your compiled executable.
  3. Set WebAppSettings.rootStaticDirectory to directory that all of your static files should be collected. You will need to deploy this directory alongside your executable. When files are collected we use a merge strategy. In the future we hope to use this to make it easy to overwrite a library's static files with your own.
  4. Set WebAppSettings.staticRoutePath to the URL to use when referring to static files e.g. "/static/".
  5. Use potcake.web.staticPath to build URLs for static assets.
  6. Call WebApp.serveStaticfiles() before running your app.
  7. Add the following lines to your dub file and setup your main entry point function to accept program arguments. Pass these arguments to WebApp.run.
postBuildCommands "\"$DUB_TARGET_PATH\\$DUB_ROOT_PACKAGE_TARGET_NAME\" --collectstatic" platform="windows"
postBuildCommands "\"$DUB_TARGET_PATH/$DUB_ROOT_PACKAGE_TARGET_NAME\" --collectstatic" platform="posix"

See collectstaticfiles for a demonstration.


Potcake provides a framework for middleware. Middleware provided can be run at any point in the request handling process.

Default Middleware

In its out-of-the-box configuration Potcake provides a set of default middleware.

useIsSecureRequestMiddleware - Record on request whether it was delivered via a secure channel.

useHstsMiddleware - Inform browsers that your app should only be visited via HTTPS.

useStaticFilesMiddleware - Serves static files.

useRoutingMiddleware - Adds the ability to route a request to a handler. Must be used with and called before useHandlerMiddleware.

useBrowserHardeningMiddleware - Harden the browser environment your web app is rendered in.

useHandlerMiddleware - Calls a selected handler after routing. Must be used with and called after useRoutingMiddleware.

When adding custom middleware take care to preserve the order recorded in WebAppSettings.middleware.

Custom Middleware

Middleware can be added via WebAppSettings.middleware. Middleware in that list are run forward and reverse in order, like layers in an onion i.e. middleware have the opportunity to run on a forward pass before their succeeding middleware is run and on a reverse pass after their succeeding middleware is run. For the following middleware definition:

settings.middleware = [
    &A, &B, &C,

middleware will be run in this order:

A -> B -> C -> B -> A

Middleware can short-circuit the chain by omitting a call to their succeeding middleware. Potcake uses this to skip routing and handling middleware when serving a static file.

To craft and add middleware, first create a MiddlewareDelegate or MiddlewareFunction. Both accept and call an HTTPServerRequestDelegate that represents the next middleware in the chain. Both should return an HTTPServerRequestDelegate that can be called by the middleware prior to it.

Next create a function that accepts a WebApp and returns a WebApp. This function must call WebApp.addMiddleware to add your MiddlewareDelegate/MiddlewareFunction. You can safely add middleware anywhere in the middleware chain e.g. pre-routing or directly pre-handling.

For example:

import potcake.web;

WebApp useMiddleware(WebApp webApp)
    HTTPServerRequestDelegate middleware(HTTPServerRequestDelegate next)
        void middlewareDelegate(HTTPServerRequest req, HTTPServerResponse res)
            // Run actions prior to the next middleware.
            next(req, res);
            // Run actions after the next middleware.

        return &middlewareDelegate;
    return webApp;

int main()
    auto settings = new WebAppSettings;
    settings.middleware = [
        &useMiddleware, // your middleware
    return new WebApp(settings)
    .addRoute("/", delegate void(HTTPServerRequest req, HTTPServerResponse res) {})


On initial setup, a Potcake WebApp accepts a settings class in the family of WebAppSettings. WebAppSettings has settings core to Potcake with the framework's defaults.

You can add your own settings by subclassing WebAppSettings and adding your own fields.

Potcake provides a way to access your settings at runtime from anywhere in your program in getSetting.

For example:

import potcake.web;

class MySettings : WebAppSettings
    string mySetting = "my setting";

int main()
    auto webApp = new WebApp(new MySettings);
    .addRoute("/", delegate void(HTTPServerRequest req, HTTPServerResponse res) {
        auto setting = (() @trusted => getSetting("mySetting").get!string)();

    return webApp.run();
Core Settings


Default: false

Signal to Potcake that your app is running behind a proxy that you trust. This matters when you are using a proxy to provide HTTPS for your app. In order for Potcake to know that a request is secure, your proxy must signal that using headers. If your proxy isn't taking control and ignoring those headers from clients then your app is open to being coerced into carrying out sensitive actions over an insecure channel. Potcake forces the developer to opt in to trusting a proxy to prevent accidentally opening up their app to exploitation.

Web App Environment

You can control the behaviour of your web app based on the environment it's running in via the WebAppSettings.environment setting. Potcake is configured out of the box to react to WebAppEnvironment values but any string value can be used.


Potcake allows for setting logging settings keyed on environment. This allows for:

  • varying logging between development and production
  • varying log levels and formats between loggers in an environment

Logging settings can be set via WebAppSettings.logging. Configured loggers can be any subclass of vibe.d's Logger.

For example:

auto settings = new WebAppSettings;
settings.logging = [
    WebAppEnvironment.development: [
        LoggerSetting(LogLevel.info, new VibedStdoutLogger, FileLogger.Format.threadTime),
    WebAppEnvironment.production: [
        LoggerSetting(LogLevel.warn, new FileLogger("application.log"), FileLogger.Format.threadTime),

Environment Variables

Potcake provides a convenience function for fetching environment variables. The function can also optionally convert variables to a given type. The interface is the same as the one for std.process.environment.get.

For example:

auto settings = new WebAppSettings;
settings.vibed.port = getEnvVar!ushort("WEB_APP_PORT", "9000");

Environment variables can be converted to booleans using the following rules:


Q - Why the name Potcake?

A - I am from The Bahamas where Potcakes are a breed of dog. They are easy to live with, sensible in their decision-making, and dependable. All great aspirational qualities for a web framework.


  • Potcake libraries that can provide templates, static files, and routes on import. This will need:
    • [ ] DIET template loading from a library
    • [ ] Static file collection from a library
    • [ ] Route inclusion from a library
  • Middleware
    • [X] Middleware system
    • Convenience middleware
      • [X] Static files
      • [ ] CSRF
      • [ ] CORS
    • [X] Post-routing middleware
    • [ ] Health-check endpoint middleware
  • Kyle Ingraham
Sub packages:
potcake:http, potcake:web, potcake:core
potcake:web, potcake:http, potcake:core
0.5.0 2023-Nov-02
0.4.0 2023-Jul-30
0.3.1 2023-Jul-30
0.3.0 2023-Jul-27
0.2.0 2023-Jul-14
Show all 8 versions
Download Stats:
  • 0 downloads today

  • 0 downloads this week

  • 0 downloads this month

  • 26 downloads total

Short URL: