Mit Randall. - Creating a Barebones Phalcon App: A simple step-by-step recipe for beginners

Lets get our Sprint kicked off by installing the core folder structure. We will also add a few empty files just so I can talk about why they are needed before you actually start writing code. This is the fastest way to get into the underlying thinking of the Phalcon framework.

Open a terminal window and go into your development directory. We will make a new folder where we want to store the app. Name it whatever you want, but if you are doing this for the first time, you may want to use my naming convention so you do not get lost.

I like to put all of my projects in a folder called Development off my main user folder. You should put your projects wherever works best for you, and it will be obvious where you can replace your folder names with mine.

cd Development

mkdir phalcon-starter

cd phalcon-starter

Remember, the Development folder is my personal location. Please use the one that works best for you.

The convention in Phalcon is to store all of your application files (controllers, models, views, configs, etc) in a folder called app and all of your publicly accessible files such as CSS, JS and images in a folder called public .

cd phalcon-starter

mkdir app

mkdir public

Phalcon is based on the Model-View-Controller (MVC) pattern for separating the core aspects of an application. Lets create the following folders under your app folder:

cd phalcon-starter/app

mkdir controllers

mkdir models

mkdir views

Controllers

Controllers hold the application logic for your app. Controllers are where you put actions that handle user interaction and determine the appropriate UI to respond back to the user. Controllers can also be used to check for member credentials, post form data, format JSON responses, handle errors and so forth.