This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Main idea

Old Zope2 products were heavily based on skins resources. A lot of additional information for those resources are taken from .metadata file, so commonly if you have a:


…you will want to have also a:


In old Zope/Plone installation (let me say “before Varnish begin to be a Plone standard”) you can use those metadata for performing associations with HttpCache objects, making the user browser to perform some cache of resources:



This product will install for you a new executable: zopemetadatamaker. Using this you can automatically create your .metadata files. when you have a lot of static images, css and javascript files this can save you some times, for example: you downloaded a big Javascript library with a lot of sub-directories inside and other related resources.

How to use

The basic use of the command is something like this:

zopemetadatamaker *.gif

This will create for you all “.metadata” related to all gif file found in the current directory. You need to know that:

  • you must provide at least one filter patters
  • the directory where files are searched is the current working directory (but you can customize this, see below).

Complete list of options

Here the full documentation:

Usage: zopemetadatamaker [options] pattern [patterns]

Bulk creation of .metadata files for Zope skins resources

  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -c METADATA, --content=METADATA
                        choose a metadata text different from default; use
                        quoting for multiline input
  -d, --default         print default metadata (if --content is not provided),
                        then exit
  -p PATHS, --path=PATHS
                        directories path where to look for metadata. You can
                        use this multiple times. Default is the current
                        working directory
  --dry-run             dry run, simply print what I would like to do
  -f, --force           force .metadata creation; if another one exists it
                        will be replaced
  -r, --recursive       search and create recursively inside subdirs

What to put in the .metadata content

The default metadata content is like this:


The %(filename)s section will be replaced with the original file name. You can use this, or omit it, when defining you custom .metadata.

I use this default content because it is the minimal “cache” information for Plone CMS static resouces.


0.1.0 (2011-04-04)

  • Initial release
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
zopemetadatamaker-0.1.0.tar.gz (9.3 kB) Copy SHA256 Checksum SHA256 Source Apr 4, 2011

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting