PhpTide is a compact PHP web framework. In this repository the framework source lives in the phptide/ directory (entry phptide/start.php); your application code typically sits in app/, with the web root in public/. The guides on this site document that core and how to use it in real projects.

PhpTide aims to bring PHP web development back to a rhythm that is simple, direct, and maintainable: express business logic clearly with as little boilerplate as possible.

What the implementation gives you

• tide\ namespace — framework classes live under phptide/ and load via load.php.
• Data access — PDO-backed models with a fluent-style API; MySQL, PostgreSQL, or SQLite from config.
• Routing — register rules per HTTP method in app/route.php; path variables merge into $_GET.
• Cache — file / Redis / Memcache drivers from config; session backends live under phptide/session/ (e.g. DB, Redis). See phptide/config.php for keys and defaults.
• Optional Composer — if vendor-composer/autoload.php exists next to your layout, it is pulled in from start.php before the legacy autoloader runs.

Design philosophy

The framework favors convention over configuration, so directories, controllers, views, and routes stay organized in a consistent way. You can get a runnable app quickly without understanding every mechanism up front.

How to read this guide

If you are new to PhpTide, follow this order: Getting started → Configuration → Controllers → Models → Views → Routing. That builds a mental model first, then dives into specifics.

Style and goals

PhpTide is not about piling on features—it is about a smooth developer experience:

• Syntax stays close to plain PHP.
• Common tasks get straightforward helpers and conventions.
• The layout is clear for teams and long-term maintenance.

    ____  __        _______     __   
   / __ \/ /_  ____/_  __(_)___/ /__ 
  / /_/ / __ \/ __ \/ / / / __  / _ \
 / ____/ / / / /_/ / / / / /_/ /  __/
/_/   /_/ /_/ .___/_/ /_/\__,_/\___/ 
           /_/