Download the PHP package eddiejaoude/dev-helper-cmds without Composer

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

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 eddiejaoude/dev-helper-cmds

Informations about the package dev-helper-cmds

Dev Helper Commands

Gitter

Useful commands for every Developer.

This abstracts the commands required for development.

For example:

If a developer/tester needs to start the webserver, then should *NOT * care if you are using vagrant or php built-in webserver. They should just run the same command (eg. make dev.server). This way, when updating the architecture, the same commands can be run, even if they are doing something slightly different or more than in an earlier version.

Usage

  1. Create a Makefile in the root of your project.

  2. Added a LOCATION parameter to the top of the Makefile

If you have brought in this Helper Library with composer, then you need to update the location of the include files.

In your main Makefile update the location parameter:

Note: must NOT end in a /

  1. Now include the commands you want to use or include all by adding the following to your Makefile

  2. Then you are done.

Below our the built-in commands.

Overriding commands

You can override these by adding to your Makefile that contains all the includes.

Combining commands to make new ones

It is also possible to combine exist or new commands with a new command:

Added Custom commands

  1. Create a directory in your project root .make/

  2. Add command files inside new directory .make/log

  3. In your Makefile include new custom files with

All done!

Built-in commands

Git commands

Composer commands

Symfony

Built-in Server
Dump logs
Database
Dump & commit assets

Example usage / override, add the following to your custom Makefile (or include)

Running tests in parallel using Robo
Running Behat tests
Running PHPSpec
Running PHPUnit

All versions of dev-helper-cmds with dependencies

PHP Build Version
Package Version
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 eddiejaoude/dev-helper-cmds contains the following files

Loading the files please wait ....