Download the PHP package fei/phing-service without Composer
On this page you can find all versions of the php package fei/phing-service. 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 phing-service
Purpose
Phing Service, build script to expose an unique script to setup system
Developer environment installation
Simply require fei/phing-service in composer
Environment configuration information
All projects can use this service to simplify its own build
Documentation
Installation
Require fei/phing-service
NB : After tag 2.*
Phing configuration
Build configuration
Add phing.xml script with :
NB : Targets could be added on this build.xml to take care about project exception
Create settings_local.ini script with minimum on root :
NB : After tag 3.* you have to prefix [CONFIG PATH] with ${project.basedir}
Override settings_local.ini :
For local usage it can be useful to override default local settings with specifics.
To do this you just have to create file named settings_local.override.ini which will :
- redefine properties
- define new properties
This file must be ignored.
Complete this script with your properties with following pattern :
Prepare config files
- Rename Config files .php to .php.dist
- Replace all environment vars to @[NAME OF CONFIG FILE].[YOUR OWN KEY]@
Before
After
- Rename Config files tests/.suite.yml to tests/.suite.yml.dist (except unit.suite.yml)
- Replace all environment vars to [YOUR OWN KEY] (without @)
Before
After
Access and coverage
Add script .htaccess on public path with :
Add include c3.php into public/index.php
NB : You have to create acceptance path too
Local run
To prepare your environment, you have to run following command :
To prepare your environment for acceptance tests, you have to run following command :
Continuousphp configuration
On Build settings pipeline fill :
DocumentRoot => /public Phing -> Build file => phing.xml
On Test settings fill on Codeception :
Environment variables
- CONTINUOUSPHP => continuousphp
- CPHP_SERVICE_APACHE => 2.4.0
- APP_ENV => dev
- CPHP_SERVICE_SELENIUM => 3.4.0-chromium
Phing Target
- local-setup-system
- setup-acceptance
- create-database (in case of acceptance tests)
- setup-coverage
Overwrite acceptance variable(s)
- qaPattern => apache24
- qaDatabase => mysql
- qaUrlPattern => 127.0.0.1
- qaBeanstalk => beanstalkd (if needed)
NB : If you have some trouble with coverage acceptance, please repport on branding-api project to check settings coverage on suites yml
On Package Settings (for deploy pipeline) :
Phing Target
- clean-build
Addons
Version >= V4.2.0
Frontend execution
In case of you have a project >Frontend/backend in the same repository, you can use this target to automaticly build into your backend build without actions of infra.
In your settings ini, you have to add :
Target to add in continuous at the "Package Settings" step
Connect key generating
If you have to plug connect on your project, simply add the private key in following property
