lib/umlaut_configurable.rb in umlaut-3.0.0beta3 vs lib/umlaut_configurable.rb in umlaut-3.0.0beta4
- old
+ new
@@ -27,10 +27,14 @@
configuration.configure do
app_name 'Find It'
# URL to image to use for link resolver, OR name of image asset in local app.
#link_img_url "http//something"
+ # string used in standard layout footer to identify your app.
+ # mark it html_safe if it includes html
+ # footer_credit "Find It service provided by <a href='http://www.university.edu/'>My University</a>".html_safe
+
# Sometimes Umlaut sends out email, what email addr should it be from?
from_email_addr 'no_reply@umlaut.example.com'
layout "umlaut"
resolve_layout deferred! {|c| c.layout}
@@ -132,27 +136,16 @@
# link resolver knowledge base, display a warning to the user of potential
# typo?
entry_not_in_kb_warning true
nightly_maintenance do
- # When nightly_maintenance will expire sessions. Default to
- # 1 day. Over-ride locally if desired, but
- # probably no reason to.
- session_expire_seconds 1.day
- referent_expire_seconds deferred! {|c| c.session_expire_seconds }
+ # How old does a request have to be to be deleted by nightly_maintenance?
+ # requests are only re-used within a session. Probably no reason to
+ # change this.
+ request_expire_seconds 1.day
-
- # Expire service responses. Service responses are only re-used by the same
- # session that generated them. But sometimes even that's too much, we
- # want to expire them eventually, say every 24 hours.
- # You can do this in two ways.
- #
- # A Number of seconds in an interval, eg:
- response_expire_interval 1.day
- #
- # Or, sometimes it's convenient to synchronize this with some other
- # process that runs on crontab. Say, expire at midnight every night:
- # response_expire_crontab_format "00 00 * * *"
+ # How long to keep FAILED DispatchServices, for viewing problems/troubleshooting
+ failed_dispatch_expire_seconds 4.weeks
end
# Configuration for the 'search' functions -- A-Z lookup
# and citation entry.