Question 1

How to pick the best Phalcon MVC structure for a new project?

Accepted Answer

Start with the 'single-factory-default' for basic apps or 'multiple' for frontend/backend separation; assess your needs for modularity, templating engines, and service configurations based on the examples provided.

Question 2

Phalcon MVC examples or Laravel's built-in structure?

Accepted Answer

Choose Phalcon examples if you prefer a C-extension framework for performance and need flexible MVC patterns; Laravel is better for rapid development with built-in tools like Eloquent ORM and Blade templating.

Question 3

How to implement custom service providers in Phalcon?

Accepted Answer

Refer to the 'single-service-provider' example, which shows a non-standard way with AbstractServiceProvider classes; it demonstrates registering services like DatabaseServiceProvider and ViewServiceProvider.

Question 4

What's the difference between simple and multi-module Phalcon apps?

Accepted Answer

Simple structures like 'simple' have one MVC set, while multi-module ones like 'multiple' separate logic into modules (e.g., frontend/backend) with shared resources, ideal for larger projects.

Question 5

Are these examples compatible with Phalcon 5?

Accepted Answer

They target Phalcon >= 3.0.x, so check the official Phalcon Docs for updates; breaking changes in newer versions might require adjustments, as these examples aren't guaranteed to be current.

Question 6

How to add authentication to a Phalcon MVC app from these examples?

Accepted Answer

These examples don't include authentication; you'd need to extend a structure like 'multiple' by adding controllers, models, and services for user management, referencing Phalcon's security components.

MVC

What is MVC?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions