denners777 / api-phalcon

dev-master 2026-10-04 02:46 UTC

Requires

• php: >=5.6
• ext-phalcon: 2.*
• cangelis/pdf: ^2.2
• filp/whoops: ^2.1
• iio/libmergepdf: ^3.0
• ilya/belt: ^2.1
• jbroadway/urlify: ^1.1
• kriswallsmith/assetic: ^1.4
• mpdf/mpdf: ^6.1
• phalcon/incubator: 2.*
• phalcongelist/breadcrumbs: ^1.2
• phpoffice/phpexcel: ^1.8
• respect/validation: ^1.1
• rollbar/rollbar: ^0.18.2
• swiftmailer/swiftmailer: ^5.4
• symfony/debug: ^3.2
• symfony/var-dumper: ^3.2
• vlucas/phpdotenv: ^2.4

MIT

• Denner Fernandes

• framework
• api
• app
• phalcon

Published on Packagist.org on 2026-10-11 06:59 UTC

README

Modular Intranet — Phalcon PHP

A legacy modular business application built with Phalcon PHP and Oracle.

Portfolio context

This repository is an older production-oriented PHP project and is kept public to document an earlier stage of my backend career.

It is not presented as a modern dependency baseline. Its value today is showing work with a modular business application, Oracle integration and a PHP ecosystem that predates my later migration toward Node.js/TypeScript.

What is inside

The application is organized into multiple business modules:

app/modules/
├── catraca/
├── cnab/
├── forms/
├── intranet/
├── nucleo/
├── otrs/
└── telephony/

This structure supported multiple internal concerns without putting the whole application into a single controller/model surface.

Stack

• PHP 5.6+
• Phalcon 2.x
• Oracle Database
• Composer / PSR-4 autoloading
• Whoops
• SwiftMailer
• Respect Validation
• PHPExcel
• mPDF / PDF tooling
• dotenv
• Rollbar

Architecture highlights

The Composer configuration uses PSR-4 autoloading:

App\ → app/

The codebase also integrates packages for:

• validation;
• email;
• spreadsheets;
• PDF generation/merge;
• error handling and debugging;
• environment configuration;
• application monitoring.

Why it remains relevant

The repository documents practical experience with:

• maintaining a modular monolithic application;
• Oracle-backed business systems;
• legacy modernization constraints;
• enterprise integrations;
• server-side document/report generation;
• PHP dependency management.

It also makes the evolution of my backend stack visible: this period was heavily PHP-focused, while later projects moved toward Node.js and TypeScript.

Running the project

Because this is a historical application, running it requires an environment compatible with its original stack, including PHP 5.6, Phalcon 2.x and Oracle connectivity.

For that reason, this repository should be read primarily as a portfolio/code-history project rather than a current starter template.

Status

Historical / maintained as portfolio evidence.

Built during my PHP backend years — preserved to show the path, not to pretend the stack never changed.