Hi,
I would like to know what are the files that are not needed when moving to production. For example the dojox folder, test directories, demo directories etc. It would be good if there were two downloads - one for developent environment and one for production environment. I need this information to justify the size of files required, remove unnecessary files for security reason etc.
Thanks
-pugal
Dojo files for production environment
Submitted by pugals on Fri, 04/11/2008 - 14:15.
- Login or register to post comments
- Subscribe post
I did a big blog post:
I wrote up a blog on SitePen site kind of outlining what you need. The script I came up with produces a fully functioning 1.1 release in 1meg of tarball.
http://www.sitepen.com/blog/2008/04/02/dojo-mini-optimization-tricks-wit...
Hope this helps.
(the plan is to roll some of the cleanup into options in the build, so this kind of thing is even easier)
Great explanation
Hi,
The blog is great. Thansk a lot.
I wish dojo includes a README or some documentation of unnecessary files in production. That way we won't have double-guess our decision.
Agreed.
The plan is to make the resultant dojo-mini release (or some form thereof) part of Dojo.
http://dante.dojotoolkit.org/mini/dojo-release-1.1.0-mini.tar.gz
_should_ be a drop-in solution if you are using Dojo 1.1 ... I'd be interested in hearing any bug reports about it's usage so we can more quickly roll the changes into the official release.
Couldn't this be just an
Couldn't this be just an additional optional build step, to clean out a production release just from everything which won't ever get downloaded by a client browser ?
Roberto
yes.
again with the "time permitting", I've meant to modify the script used to create -mini release to work from util/buildscripts/ folder to run against ../../release/dojo/* so you can just do something like:
cleanup.sh ../../release
but getting it into the actual build mechanism would be ideal.