To get an set options, either use \HotMelt\Config::get() and \HotMelt\Config::set()`, respectively, or take advantage of the fact that \HotMelt\Config allows arbitrary method overloading

\HotMelt\Config parses these configuration files:

• Site/config.php
• Site/config-<DOMAIN>.php

For a host name beginning with www., \HotMelt\Config will also try to load the configuration file for the corresponding host name without www..

Create a cookie object and access its value with the value property. Use \HotMelt\Cookie::update() to change its value and send the cookie back to the client, or use \HotMelt\Cookie::delete() to delete the cookie.

Middleware can register for hooks to intercept requests.

Extensions include a wrapper around \PDO::prepare() that wraps statements in an instance of \HotMelt\PDOStatementDecorator and support for quoting identifiers (\HotMelt\PDO::quoteIdentifier()).

The PersistentObject class prefers convention over configuration. This is an overview of the conventions that the PersistentObject class establishes and how to override them:

• Objects are read from and written to a table that is the plural form of the subclass name (without the namespace prefix). Override the tableName() method to change this.
• Objects have a primary key (assumged to be an auto-incrementing integer) named id. Override the primaryKey() method to change this.
• Some methods allow you to specify a \HotMelt\PDO object for database access. If not PDO is given, the PDO returned from the defaultPDO() class method is used. The default value returned by this method is null, however, so you will have to override this method to use a default PDO.

Note that you should not directly create a new persistent object instance. Use the findBy...() and insert() methods to retrieve existing objects or create new ones.

Routes are declared through the interfaces provided by the \HotMelt\Route class. HotMelt will automatically load Site/routes.php, so you should use that file to declare routes.