Add Gulp Plugin for resource installation

[webmozart]

The command puli resource --install and the installer-related functionality should be removed from Puli. Instead, this functionality should be provided by a Puli plugin for Gulp (e.g. puli/gulp-plugin). One idea to implement this is to generate a Gulp configuration file and use that in Gulpfile.js.

Basically, we have the following information about public resources in Puli packages:

• Paths (or globs) of public directories, e.g. res/public, vendor/acme/blog/res/public
• The location of the document root(s) where they should be published, e.g. public_html, ssh://..., ...
• The directory path where each directory should be published in the document root, e.g. /, /blog, ...

The Gulp plugin should move the responsibility of publishing paths to Gulp. The goal is that you can run gulp or gulp watch and have Gulp doing both your asset transformation rules (e.g. res/scss -> res/public/css, configured by hand) and the publishing (e.g. res/public/css => public_html/css, configured by the plugin) whenever a file changes.

In a first step, only publishing to local directories (e.g. /path/to/var/www/public_html) needs to be supported. In a second step, publishing to remote filesystems would be great.

[webmozart]

cc @kitsunet

[hason]

It would be great to provide a webpack loader or automatically register path aliases http://webpack.github.io/docs/configuration.html#resolve-alias

[webmozart]

@hason Sounds like a good idea! Do you want to work on that? If yes, we should discuss this in a separate issue.

[temp]

Any reason why you prefer gulp over grunt?

[webmozart]

@temp I haven't used Grunt, but I was told that Gulp is easier to use. For Puli, I think we need plugins for most of the commonly used frontend tools (Gulp, Grunt, Brunch, others?).

[temp]

We can help out with grunt, I guess ;-) Don't know brunch. But now I'm hungry!

[webmozart]

Cool :) see #97

[tgalopin]

I'll try to work on the Gulp one, but I never wrote such plugin so I'll have to learn a lot before being able to propose something useful :) . If someone more experienced is motivated to start something, I am very open to give a hand!

[wouterj]

Feel free to ping me if you need help, @tgalopin

[tgalopin]

I will, thanks @WouterJ!

[felixkiss]

@webmozart broccoli.js is another one.

[tgalopin]

@mickaelandrieu started to work on this here: https://github.com/puli/gulp-plugin.

[maciekpaprocki]

I am more then happy to develop that, if someone will provide me with example config file + tasks that need to be done. No experience with puli, tons of experience with gulp :)

So, let's say at the start task to observe will be js css third party (bower/npm)

Should we target other things like less scss sass css4 coffescript (i cannot really think of anything else now, but it's better if php developers could use standardised way of developing and almost everyone is using preprocessors)

[webmozart]

@maciekpaprocki Awesome! We're hanging out in https://gitter.im/puli/issues right now, join us if you like!

[webmozart]

@maciekpaprocki Any update?