Re: Alioth: html output dir linked to vasks???
On Thu, Oct 13, 2011 at 09:40:27AM +0200, David Paleino wrote:
> > However, I would like to get the tasks pages working *before* we have
> > sorted out this. So I would love to revert your change right now
> > (risking that postcommit hooks will not work for the moment - PET should
> > keep on working if you copy the code manually ... at least I think so).
>
> PET should work nevertheless. I just thought about fixing a "hidden" bug while
> I was at it: the HTML pages were not updated anymore after the alioth split,
> and the symlink fixed it.
What exact HTML pages are you talking about? Auto generated ones or
static pages?
> > I'm somehow tempted to revert the symling soonish because I need working
> > tasks pages (nowish) because I need to demonstrate something here. For
> > the moment nothing should be broken by this change back because the
> > working code is just populated, right?
>
> Well, everything happens on vasks, so even if the web part was broken, it
> wouldn't appear (because pages are served from wagner). So yes, it's safe :)
I'm afraid I do not understand what you mean by "everything happens on
vasks". Your trick enabled somehow writing to the (wagner-)webspace.
What happens if you are not able to write any more? My guess there is
no need to write something on wagner and the pages are just delivered
by executing code (on vasks). Is this correct.
> > BTW, did you created a copy of the old htdocs dir before creating the
> > symlink?
>
> No, I didn't -- I supposed wagner's htdocs were still dated ~May 2011, so I
> thought they were old files, and just rm'ed them. Sorry :/
No real problem but actually the content of tasks/ was dated from the
day before. :-) The only thing is that (for a reason to be
investigated) UDD is currently terribly slow and recreating the tasks
pages takes 10 times longer than it should take.
> We can remove the symlink, make a copy of htdocs/ from vasks to wagner, and then
OK, I'll do so.
> run "make publish" to update tasks pages once again.
To make things more clear: This "make publish" works for the static Blends
documentation. The tasks pages are created by scripts sitting on wagner
and are run by a cron job. (However, to update these scripts I do also
a manual publishing mechanism like "make publish" instead of bringing it
into production by a single commit. :-))
Kind regards
Andreas (just now reverting the symlink)
--
http://fam-tille.de
Reply to: