Download the PHP package 3ev/phingy without Composer
On this page you can find all versions of the php package 3ev/phingy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phingy
Phingy
Phingy is a small collection of build scripts which you can mix together differently depending on your project. To use these scripts, you include the required ones in your build script starting with your own project.xml.
Installation & dependencies
Phingy is installed via Composer. Add the following to
your project's composer.json and run composer install:
You'll then be able to run Phing using
'Skel' files
Phingy will automatically generate files from .skel files anywhere in your project.
These files can include Phing properties which will be replaced with their actual
values at compile time.
You may for example want to create an Apache vhost config file for your project, which you'll be able to commit to source control without having to including any environment specific config. Like so:
Database tasks & S3
If you'd like to make use of the database tasks that push/pull database dumps from Amazon S3, you will need to install the Pear Amazon S3 package:
This will allow you to backup and download your full database to/from S3 using:
There are numerous other database tasks that make it easy to configure a MySQL database for your project.
Setting up a webserver
Phingy includes a build:server task which will by default configure and install
Apache configuration for your project.
Config will be symlinked from config/httpd.conf to /etc/apache2/sites-enabled,
so you can commit a file to version control (or use a .skel extension) and simply
run
to start your project running on Apache.
Platform specific tasks
Phingy includes a few 'platform' specifc task sets, as followss:
- typo3 Typo3 specific tasks (includes db). Will set up TYPO3 on build, and provides some utility methods.
- sphinx Sphinx specific tasks. Provides tasks to index Sphinx data for the project.
- laravel Laravel specific tasks. Provides tasks to work with the Laravel framework
Setting up your project with Platforms
When you run composer install, you will be prompted to pick a template to use
for your project. Selecting a template will create a file called project.xml in
your project's config/ directory.
The project.xml file includes a number of hooks you can add to for project-specific
tasks. Currently, These are:
Each platform includes each of these hooks as well, of the form [platform]:build:before etc.
If you'd like to make use of a platform, simply include it with:
and then call each of its hooks in your project-specific hooks:
Note: If you pick a non-default template (like 'typo3'), all of this will be handled for you.
Adding your own project specific tasks and config
You can add any of your own tasks in config/project.xml. These should be namespaced
with project: for convention. You can either add standalone tasks, or call them
in any of the available hooks.
Overriding existing tasks
If you need to, you can override built in tasks by creating a new task with the
same name in your project.xml. You shouldn't have to do this though, as the
built in hooks provide enough flexibility for you to customise tasks.
Adding extra config
You add should any project specific config to config/project.properties if possible.
If you need to prompt the user for it during build, you can do so in the
project:config hook.
About ./build.xml
build.xml sits in the root of your project, and is symlinked from vendor/.
You should add this file to your .gitignore.
