@jaz303 sorry for a delayed reply - lost this thread for a while.

In my company we use phake for building all our client projects. Some things are reusable everywhere (like git tasks, for example). Some are reusable only on the subset of projects (like WordPress-specific tasks, for example). And some are unique to a project.

Currently, we use QoboLtd/phake-builder for all the things that are common. And then we use a variety of boilerplate/template projects (for example: QoboLtd/project-template-wordpress which add platform-specific tasks to Phakefile.

Overall, this works, but lacks elegance and flexibility. As you can see, for example, in QoboLtd/phake-builder we have a whole bunch of common tasks, which we separate into different Phakefiles (Phakefile.git, Phakefile.mysql, etc) and then we load all of them from the central one.

It would be awesome if we could break that up into some kind of Phake plugins (a plugin to share git tasks, a plugin to share mysql tasks, etc), and then include those plugins with composer as needed for each project. A few tools already do exactly that using composer installers, which is the preferred way. Some other projects use fixed vendor name - for example WordPress themes and plugins can be installed so from WordPress Packagist.

Grouping common phake tasks and separating them into modules/plugins would make it easy to share them between projects, companies, and people. I think it will also help increase phake adoption, since it will be easier for projects to ship their specific tasks (WordPress or CakePHP, for example), while reusing other common tasks (like git and MySQL).

From what I can see, Phing is popular this way now. And I think part of it is because it bandles common tasks for ssh, ftp, version control, etc right into the tool, and makes it easier to add/customize them too.

Uh oh!

Is phake alive #57

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions