-
-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplified Configuration System for multiple collections #55
Labels
Milestone
Comments
ikreymer
added a commit
that referenced
this issue
Feb 25, 2015
…onfig! config.yaml file now optional, add default_config.yaml which for default settings #55
ikreymer
added a commit
that referenced
this issue
Feb 25, 2015
ikreymer
added a commit
that referenced
this issue
Feb 25, 2015
ikreymer
added a commit
that referenced
this issue
Feb 25, 2015
ikreymer
added a commit
that referenced
this issue
Mar 16, 2015
config override: when loading from coll-specific config.yaml, resolve relative paths to that collection, not to root #55
New config system works in 0.9.0beta! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add an optional 'convention over configuration' system for setting up collections of warcs and cdx files..
Currently, setting up multiple collections can be a bit tedious. For example, configuring two collections, each with custom set of cdx, warcs, search page and banner might look like this:
With the new convention system, the collections can instead be configured implicitly within a
collections
directory, eg:collections/coll1/
,collections/coll2
, and each having aindexes
,archive
and an optionaltemplates
subdir.Edit: changed
cdx
->indexes
,warcs
->archive
in new config systemThe text was updated successfully, but these errors were encountered: