Andrew Golightly wrote:
So let me see if I understand this..
You have your publication directory containing all the source files.
Then you build it and files get placed into the build directory. Then
any future changes you make from the GUI only affect the build
directory? So the source files are only a once off kind of thing? And if
you wanted to do any backups, it would be the build directory you would
want to backup?
iiuc, yes. at least that is the case with lenya 1.4.
my test setup currently runs as follows:
* create a user and group "lenya"
* make the entire build directory owned by root and not writable to
anyone else
* chmod -R lenya:lenya build/...<pub>/content/*
* chmod -R lenya:lenya build/..<pub>/config/ac/*
* run the servlet as user lenya (su -c "./lenya.sh" lenya).
everything in those lenya-owned directories can change at runtime, so
they need to be backed up.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
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]
