El dia dv 18 jul 2014 15:50:00 CEST, Mark H. Wood va escriure:
> [...]
> Since DSpace needs to be configured for storing stuff anyway, I long
> ago invented a dspace.cfg property "dspace.var" and recoded all of the
> writable paths in dspace.cfg to interpolate ${dspace.var} rather than
> ${dspace.dir}. I'd like to suggest adopting this as standard
> practice, to help sites that would like to separate code from data for
> manageability or security reasons or just because it's an ingrained
> habit. :-) Current behavior can easily be maintained by shipping a
> config that defines "dspace.var = ${dspace.dir}"
>
Hi Mark,
I also set up my DSpace servers in this way. In my case I use
dspace.data.dir like your dspace.var, but also an additional
dspace.log.dir for the logs. So I think it would be nice to be able to
set up DSpace in this way out of the box.
Cheers,
Àlex
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
