https://github.com/ryu22e/slim-skeleton-phpunit
Slim Framework skeleton application
https://github.com/ryu22e/slim-skeleton-phpunit
Last synced: about 1 month ago
JSON representation
Slim Framework skeleton application
- Host: GitHub
- URL: https://github.com/ryu22e/slim-skeleton-phpunit
- Owner: ryu22e
- Created: 2015-01-31T05:51:18.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2015-02-06T13:27:16.000Z (over 11 years ago)
- Last Synced: 2025-01-18T13:33:30.098Z (over 1 year ago)
- Language: PHP
- Size: 129 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
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 ryu22e/slim-skeleton-phpunit [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 test
After install the application, run this command from the directory.
make test
Test codes are in `tests/`.
## 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).