Some zf2 modules have public directories for distribution of resources such as js/css/images. What is best practice for making these resouces available to the applicaiton?
I would like it so that these resources were automatically available through http://mysite.com/[moduleName]/
. For example,
root/public/js/sitescript.js
--> http:\\mysite.com\js\sitescript.js
root/module/mymodule/public/js/modulescript.js
--> http:\\mysite.com\mymodule\js\modulescript.js
root/vendor/vendormodule/public/js/vendorscript.js
--> http:\\mysite.com\vendormodule\js\vendorscript.js
Should these resources be copied to the root/public directory? Manual copying will be painful, and I doubt an automated build process to merge the directories would be very practial either.
Perhaps there is some magic that can be worked with httpd.conf or .htaccess?
Perhaps symlinks are the solution? But, symlinks are not straight forward to get going on a Windows platform, and would need to be created manually for each individual module.
There are many ways of doing it.
In my opinion, Assetic is a waste of computing performance, and a really bad fit for this simple problem.
The problem, as stated, is accessing /public from modules.
My solution is the following:
Edit htdocs/yoursite/public/.htaccess to add this line right after RewriteEngine On:
Edit htdocs/yoursite/public/index.php and add this code right after chdir(dirname(DIR));:
Usage: /resource/moduleName/path
Example: http://yoursite.com/resource/Statistics/css/style.css will read the actual css from yoursite/module/Statistics/public/css/style.css.
It's fast, secure, doesn't need you to specify any paths in config, needs no installation, doesn't rely on 3rd-party maintenance, and needs no helper in view. Simply access /resource from anywhere! Enjoy :)
You could try using phing to manage your build process and have it automate it all. You'd have to write the build script but afterwards it would just be like hitting play on a cd player.
Of course for testing it would be a pain.
There are 4 ways of handling this:
public/
directorypublic/
directoryUse an asset-manager module, such as one of the following:
public/
dir at deploy time