2010/11/17 Fridrich Strba <fri...@bl...>:
> Hello, good people.
>
> Since the shell access on sourceforge.net is now a bit more difficult to
> script, I came with a different approach to updating the web-pages:
>
> For libwpd: I cloned a read-only libwpd-www git repository to htdocs
> directory and updating is done basically by pushing your local git to
> the server and then pulling it from the shell on the web-space.
>
> For libwpd: I checked out the libwpg-www CVS repository to htdocs and
> the updating is done by committing into the server CVS repo and updating
> it on the web-space.
I assume you mean libwpg here. We really should just by using git for
everything. It looks like I forgot to convert all the modules for
libwpg: I'll try to get to this later tonight.
> This has two advantages:
>
> 1) I hope that it helps us to keep the git repos on the server in sync
> with our local git repos which does not seem to have been the case right
> now :)
Oops, guess I forgot to commit my later changes.
> 2) It works around the new way of accessing the shell services on
> sourceforge.net, where one has to create the shell using "ssh -t
> USERNAME,PR...@sh... create" before being able to
> access that shell for 4 hours. After which it is again destroyed :)
>
> I hope I did not mess up anybody
For libwpd, I'd actually automated the process of updating the web
site using the sync-me script, unfortunately that didn't get pushed:
#!/bin/bash
[ -z $1 ] || UNAME=$1
scp ./*html ./*png ./*jpg ./*css ./*dia
$UNAME,li...@we...:/home/groups/l/li/libwpd/htdocs
ssh $UNAME,li...@we... chmod g+w
/home/groups/l/li/libwpd/htdocs/*
I like the idea of always using what's stored in git for the web site.
Maybe we could write a new shell script that does the pull for you
automatically? What's the manual procedure you're currently using for
that?
--
William Lachance
wr...@gm...
|
