This is a proof of concept maven overlay that allows OpenWayback to be configured using a simple pywb-style YAML file.
collections:
testcoll: /data/example/
coll2:
index: /data/cdx/
resource: /data/warcs/
remotecoll:
index: http://cdx.example.org/cdx/
resource: http://warcs.example.org/warcs/
# While YAML is not quite as flexible as Spring XML you can call setters
# on bean-like objects and pass arguments to constructors.
# So the same sort of mechanisms can be used to enable custom
# implementations of some components.
#
# Obviously this power should only be used if you have to, as
# it couples the configuration to class names.
locationdb:
index: /data/cdx/
resource: !!org.archive.wayback.resourcestore.LocationDBResourceStore
db: !!org.archive.wayback.resourcestore.locationdb.RemoteResourceFileLocationDB
- http://example.org/location-db
surt_ordered: truePut some WARCs and CDX files somewhere. Create a config.yaml containing a collection:
collections:
example: /data/warcs-and-cdxes/
Either deploy to app container (Jetty, Tomcat) or just run:
mvn jetty:run -Dwayback.config=config.yamlSet the path to your config.yaml using the wayback.config system property,
servlet context init paramter or the environment variable WAYBACK_CONFIG.
Hit http://localhost:8080/example/ in your browser.
- Simple and readable
- Approachable for non-programmers (and arguably for most programmers too!)
- Decouples the configuration format from implementation details of the application (class, property names) allowing refactoring and deprecation
- Potential for better error messages and deprecation warnings
- Pywb and (Open)Wayback could share a common configuration subset
These are trivially fixable, I just haven't gotten around to it as this is a proof of concept.
- No root index page.
- Error if you don't have a trailing slash on the collection URL
- Only a few things can be configured.
- Probably lots of other issues, I haven't tested this much.