Trongate PHP Framework Docs
Introduction
Basic Concepts
Understanding Routing
Intercepting Requests
Module Fundamentals
Database Operations
Templates
Helpers
Form Handling
Form Validation
Working With Files
Image Manipulation
Working With Dates & Times
Language Control
Authorization & Authentication
Tips And Best Practices

Working With Third-Party Libraries

Trongate doesn’t need Composer. It doesn’t need Packagist. It doesn’t need any third-party code to work flawlessly.

But you’re not trapped in 1999 either. Use anything you want - Composer packages, npm libraries, random GitHub repos, whatever. Trongate won’t stop you. It just won’t depend on them.

Why Trongate Stays Independent

  • Runs forever - even if GitHub, Packagist, or the entire internet disappears tomorrow.
  • No surprise updates breaking your app at 3 AM.
  • No abandoned dependencies turning into security holes.
  • You own your codebase. 100%.

Native PHP is lean by design. Most things you’re tempted to install already have a faster, cleaner solution in pure PHP.

When to Reach for a Package

  • You need battle-tested code
  • You require third-party SDKs (for example, Stripe/AWS etc)
  • You’re building something complex that already has a mature library

Otherwise? Write it yourself. That's the Native PHP way!