hmm. if you do not back up the files in the lenya "working tree" under
<lenya home>/build/lenya/webapp/lenya/pubs/<my-publication>, how do you
back up your content?
i'm also a little uneasy about this mixture of "program code" and data
in the lenya working tree, but the only clean solution i can see is to
symlink all work, content and passwd dirs to some writable location and
keep the rest read only. how do the other lenya users keep their
installations secure?
---
Yes, ideally you would be able to specify a 'content' directory somewhere
other than under your publication (ie tomcat deployment). Symlinks
unfortunately have proven to be a problem where I work because of the fact
that our 'authoring' and 'live' environments are actually on two different
servers and you have to be real careful when deploying/taring/ftping
directories with symlinks. We are also aiming towards a method of updating
our source, redeploying onto our other box without having to copy all
current content out of the deployment, redeploy lenya & source, repopulate
content directories. Its a structural limitation of lenya that shouldnt
really be there (see discussion we've had on this a few months ago .. sorry
don't remember the topic of post).
Right now we just keep good backups... other than that .. no real policy.
Vica
PS: By content I mean anything that can be changed 'realtime'
--
"Án nýrra verka, án nútimans, hættir fortíðin að vekja áhuga."
"Without new works, without the present the past will cease to be of
interest."
- Ásmundur Sveinsson (1893-1982)
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
