Hi Lenya devs,
here's a summary of the IRC session. The IRC log can be viewed at
http://wiki.apache.org/lenya/IrcLogDocuPublication
The topic was the migration of our website to Lenya.
There was a consensus among the participants that we should migrate to
Lenya, mainly for the following reasons:
- Test scenario for collaborative editing (eat our own dogfood)
- Marketing
Conditions:
===========
- The content must be stored in the SVN repository.
- We can't commit from the zones server.
- We can't allow public access.
Issues:
=======
The central question is if we should run Lenya on the zones server or on
the local machine.
Advantages and disadvantages of the zones server:
(+) Testing scenario for collaborative work
(+) No synchronization via SVN after each change necessary
(-) Difficult SVN commit scenario
(-) It's hard to let the author of a change be the committer
Apparently most people could live with the circumstance that the author
of a change is not the committer.
When running the app on the zones, every once in a while someone would
have to commit the content:
- Copy the content from the zones server to the local sandbox via scp
- Commit the changes from your local sandbox
- Do an SVN update on the zones server
It would be discouraged to edit locally, so that SVN conflicts on the
zones server can be avoided. If conflicts occur, they would have to be
resolved manually on the zones server.
Another issue is revision control. One option would be to set Lenya's
revision history length to 0 (i.e. no backups). This means that only SVN
is used for versioning. Rolling back would mean (a) doing it manually in
the SVN sandbox on the zones server or (b) paste old content in the
source editor.
Please add more information in case I forgot something. TIA!
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
