https://github.com/lornajane/php-oop-demo

Code samples to accompany myt OOP PHP courses.
https://github.com/lornajane/php-oop-demo

Last synced: 20 days ago
JSON representation

Code samples to accompany myt OOP PHP courses.

• Host: GitHub
• URL: https://github.com/lornajane/php-oop-demo
• Owner: lornajane
• Created: 2014-03-01T21:43:59.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2014-03-13T12:57:27.000Z (over 10 years ago)
• Last Synced: 2024-10-11T23:13:39.336Z (about 1 month ago)
• Language: PHP
• Size: 969 KB
• Stars: 2
• Watchers: 1
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Slim Framework Skeleton Application

Use this skeleton application to quickly setup and start working on a new Slim Framework application. This application uses the latest Slim and Slim-Views repositories. It also uses Sensio Labs' [Twig](http://twig.sensiolabs.org) template library.

This skeleton application was built for Composer. This makes setting up a new Slim Framework application quick and easy.

## Install Composer

If you have not installed Composer, do that now. I prefer to install Composer globally in `/usr/local/bin`, but you may also install Composer locally in your current working directory. For this tutorial, I assume you have installed Composer locally.

## Install the Application

After you install Composer, run this command from the directory in which you want to install your new Slim Framework application.

    php composer.phar create-project slim/slim-skeleton [my-app-name]

Replace [my-app-name] with the desired directory name for your new application. You'll want to:

* Point your virtual host document root to your new application's `public/` directory.

* Ensure `logs/` and `templates/cache` are web writeable.

That's it! Now go build something cool.

## How to Contribute

### Pull Requests

1. Fork the Slim Skeleton repository

2. Create a new branch for each feature or improvement

3. Send a pull request from each feature branch to the **develop** branch

It is very important to separate new features or improvements into separate feature branches, and to send a

pull request for each branch. This allows us to review and pull in new features or improvements individually.

### Style Guide

All pull requests must adhere to the [PSR-2 standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md).