Paths for resources are hard-coded, requiring the app to reside in a very specific location on the user's hard disk

[machawk1]

Potentially run a setup on first launch to write these files, much like a Heritrix job's XML is generated when a one-off crawl is initiated.

[machawk1]

Consider using the user's /Library directory in OS X or giving the ability to set these values on first start.

[machawk1]

QuickSilver uses this approach (see attached pic).

[machawk1]

A templating system like Mustache ( https://github.com/defunkt/pystache ) to allow these paths to be configured on first-run or re-configured in the app.

[machawk1]

Another clever method taken by Kaleidoscope:

[machawk1]

Sawood's proposed modification to wayback.xml would remedy this issue. Upon launch of the WAIL binary, the current path of the binary could set system-level environment variables, which would then be read in the Spring file here.

Relevant OpenWayback ticket: https://github.com/iipc/openwayback/issues/217

wayback.xml

    wayback.basedir=#{systemEnvironment['WAYBACK_BASEDIR']?:'/tmp/openwayback'}
    ...

    wayback.archivedir.1=${wayback.basedir}/files1/
    wayback.archivedir.2=${wayback.basedir}/files2/

    wayback.url.scheme=#{systemEnvironment['WAYBACK_URL_SCHEME']?:'http'}
    wayback.url.host=#{systemEnvironment['WAYBACK_URL_HOST']?:'localhost'}
    wayback.url.port=#{systemEnvironment['WAYBACK_URL_PORT']?:'8080'}

[machawk1]