gitignore/ZendFramework.gitignore

# Composer files
composer.phar
vendor/

# Local configs
config/autoload/*.local.php

# Binary gettext files
*.mo

# Data
data/logs/
data/cache/
data/sessions/
data/tmp/
temp/

# Legacy ZF1
demos/
extras/documentation
Created Zend Framework 2 gitignore file 2013-12-03 08:47:58 -05:00			`# Composer files`
			`composer.phar`
			`vendor/`

			`# Local configs`
Updated Zend Framework gitignore as per docs ``` data/: This directory provides a place to store application data that is volatile and possibly temporary. The disturbance of data in this directory might cause the application to fail. Also, the information in this directory may or may not be committed to a subversion repository. Examples of things in this directory are session files, cache files, sqlite databases, logs and indexes. ``` As per docs... http://framework.zend.com/manual/2.3/en/ref/project.structure.html 2014-07-31 02:42:20 -04:00			`config/autoload/*.local.php`
Created Zend Framework 2 gitignore file 2013-12-03 08:47:58 -05:00
			`# Binary gettext files`
Fixed binary gettext files rule: .po -> .mo 2014-08-21 08:26:02 -04:00			`*.mo`
Created Zend Framework 2 gitignore file 2013-12-03 08:47:58 -05:00
			`# Data`
Updated Zend Framework gitignore as per docs ``` data/: This directory provides a place to store application data that is volatile and possibly temporary. The disturbance of data in this directory might cause the application to fail. Also, the information in this directory may or may not be committed to a subversion repository. Examples of things in this directory are session files, cache files, sqlite databases, logs and indexes. ``` As per docs... http://framework.zend.com/manual/2.3/en/ref/project.structure.html 2014-07-31 02:42:20 -04:00			`data/logs/`
			`data/cache/`
			`data/sessions/`
			`data/tmp/`
Created Zend Framework 2 gitignore file 2013-12-03 08:47:58 -05:00			`temp/`
Included Zend Framework 1 rules 2014-05-11 07:00:31 -04:00
Updated Zend Framework gitignore as per docs ``` data/: This directory provides a place to store application data that is volatile and possibly temporary. The disturbance of data in this directory might cause the application to fail. Also, the information in this directory may or may not be committed to a subversion repository. Examples of things in this directory are session files, cache files, sqlite databases, logs and indexes. ``` As per docs... http://framework.zend.com/manual/2.3/en/ref/project.structure.html 2014-07-31 02:42:20 -04:00			`# Legacy ZF1`
Included Zend Framework 1 rules 2014-05-11 07:00:31 -04:00			`demos/`
			`extras/documentation`