PHP download

Download the PHP package lasselehtinen/recipes without Composer

On this page you can find all versions of the php package lasselehtinen/recipes. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download lasselehtinen/recipes
More information about lasselehtinen/recipes
Files in lasselehtinen/recipes

Vendor lasselehtinen
Package recipes
Short Description 3rd party deployer recipes
License MIT
Homepage https://github.com/lasselehtinen/recipes

Keywords deploy deployment newrelic deployer slack recipes cachetool

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

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.

Please rate this library. Is it a good library?

Example code of lasselehtinen/recipes

Informations about the package recipes

Deployer Recipes

This repository contains third party recipes to integrate with deployer.

Using these recipes

First install this repository as a dev dependency.

For Deployer 3.x

For Deployer 2.x

Include the recipes to your will.

Recipes

Recipe	Docs	Usage
cachetool	read	`require 'vendor/deployphp/recipes/recipes/cachetool.php';`
local	read	`require 'vendor/deployphp/recipes/recipes/local.php';`
newrelic	read	`require 'vendor/deployphp/recipes/recipes/newrelic.php';`
rabbit	read	`require 'vendor/deployphp/recipes/recipes/rabbit.php';`
rsync	read	`require 'vendor/deployphp/recipes/recipes/rsync.php';`
slack	read	`require 'vendor/deployphp/recipes/recipes/slack.php';`
configure	read	`require 'vendor/deployphp/recipes/recipes/configure.php';`
hipchat	read	`require 'vendor/deployphp/recipes/recipes/hipchat.php';`

Contributing a recipe

All code contributions must go through a pull request and approved by a core developer before being merged. This is to ensure proper review of all the code.

Fork and clone.
Create a branch.
- If the recipe is for Deployer 3.x then create your branch based on master
- If the recipe is for Deployer 2.x then create your branch based on the 2.x branch
Add your recipe to the recipes folder, it must be licensed as MIT.
Add documentation in Markdown for your recipe to the docs folder, you can base your documentation from cachetool.md as it is fairly complete.
Add your recipe to the table above in README.md, please use alphabetical order.
Commit, push and send us a pull request.
You can use the documentation of your recipe as a description to your pull request.

To ensure a consistent code base, you should make sure the code follows the PSR-2.

Recipe Do's and Don'ts

For easier integration in existing project, and fewer changes in your recipe and/or docs for it, you should try and follow this general guidelines:

Use short file names for recipes. Eg ftp instead of ftp_upload_to_server_recype_by_me
Prefix all tasks in recipe with recipe name. if You have task named mytest in myrecipe it should be named myrecipe:mytest
Use global settings keyed by your recipe name. If You have one setting, name it the same as Your recipe. If You have multiple settings, use associative array
Use environment variables prefixed by Your recipe name. If You have environment varaible named better_path in recipe myrecipe, call it myrecipe_better_path
Do not override existing tasks (for example - those in common.php). Instead document throughtly how tasks from your recipe can be integrated into workflow
If your recipe depends on another (be it included in deployer or 3rd party) - document it throughtly. It's better for user to use require_once in deploy.php, rather than force dependecies.

License

Licensed under the MIT license: http://www.opensource.org/licenses/mit-license.php

All versions of recipes with dependencies

PHP Build Version

Package Version

Version 3.1.4 Release 08. Jun 2016
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of recipes from vendor lasselehtinen

No informations.

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package lasselehtinen/recipes contains the following files

Loading the files please wait ....