[OGo-Developer] New Website Exporter

[Helge Hess]

On Feb 14, 2007, at 21:42, Marcus M=FCller wrote:
> On 14.02.2007, at 20:46, Helge Hess wrote:
>> My basic plan is to somehow automate the publishing process. So =20
>> that a checkin in Svn automatically triggers a reexport of the =20
>> site to a staging area. This should make contributions to the =20
>> website much easier.
> This could be easily achieved with a post-commit hook. Ideally, =20
> this would trigger the publishing stage in an  asynchronous =20
> fashion, i.e. via 'atrun'. It's probably _very easy_ to implement =20
> this.

Actually what I would like to have is a staging area per user. So =20
that you commit in your branch and a few moments later some Apache on =20=

developer points to the export.

Well, and if you are happy with the results, you would 'svn cp' a =20
branch to some specific directory, eg '/live/updated-news-20070210'. =20
Then a script would run and update the live site picking up the =20
latest directory from the '/live' files.

I'm not perfectly sure about how to do the second step in the best =20
possible way. In theory a  real branch which gets merged would be =20
better. But thats not really what we need, we really want to fully =20
replace the branch. And I don't think that you can run
   rm /live
   cp ... /live
in one Svn transaction, but I'm not sure.


Something like this. If you want to implement it, cool! You should =20
have all the required accounts to do it? ;-)

Greets,
   Helge

PS: obviously excessive commits shouldn't lead to excessive exports ;-)
--=20
Helge Hess
http://www.helgehess.eu/