You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Torsten Schlabach <ts...@apache.org> on 2005/03/04 20:18:43 UTC
Maintainance of the Lenya Website (lenya.apache.org) again
Dear all,
there are still two issues which I am concerned with:
1. The cron job to update minotaur:/www/lenya.apache.org/ with
svn.apache.org:/repos/asf/lenya/site seems to to run any more on a
regular basis.
@Thorsten as the owner of that cron job: Is this by purpose, for any
known reason or should we consider this a problem. If we consider it a
problem, what can we do to fix this?
2. I has asked this before but got no answer: Is anyone positive that
ASF would object to install forrst on minotaur and generate the /site
from /docu automatically or on demand, but server-based?
Regards,
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Torsten Schlabach wrote:
> 1. The cron job to update minotaur:/www/lenya.apache.org/ with
> svn.apache.org:/repos/asf/lenya/site seems to to run any more on a
> regular basis.
>
> @Thorsten as the owner of that cron job: Is this by purpose, for any
> known reason or should we consider this a problem. If we consider it a
> problem, what can we do to fix this?
i always ssh in and do a svn up in /www/lenya.apache.org when i commit
something to site
> 2. I has asked this before but got no answer: Is anyone positive that
> ASF would object to install forrst on minotaur and generate the /site
> from /docu automatically or on demand, but server-based?
that has been in discussion forever:
http://www.mail-archive.com/dev@forrest.apache.org/msg00207.html
it now seems there *is* a forrest instance running somewhere. best to
ask on forrest-dev what the latest is. i also noticed that the cocooners
are interested in getting this to work
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> NOTE: CC to forrest-dev because of point 2 from T. Schlabach.
>
> On Fri, 2005-03-04 at 20:18 +0100, Torsten Schlabach wrote:
> > there are still two issues which I am concerned with:
[snip]
> > 2. I has asked this before but got no answer: Is anyone positive that
> > ASF would object to install forrst on minotaur and generate the /site
> > from /docu automatically or on demand, but server-based?
>
> We have one installed but on a machine that is outside of the live
> system. Trying to say we can not use it neither for deployment nor for
> live feed of our side.
Torsten, there is a move to get a better ASF publishing infrastructure.
If we were able to run forrest on minotaur for general use, then we
would have done it long before this. No, we need to wait until other
ASF machines are available, then minotaur can rsync a produced
website from there.
See the current proposal and demo:
http://forrest.apache.org/proposal-asf-publish.html#demo
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> NOTE: CC to forrest-dev because of point 2 from T. Schlabach.
>
> On Fri, 2005-03-04 at 20:18 +0100, Torsten Schlabach wrote:
> > there are still two issues which I am concerned with:
[snip]
> > 2. I has asked this before but got no answer: Is anyone positive that
> > ASF would object to install forrst on minotaur and generate the /site
> > from /docu automatically or on demand, but server-based?
>
> We have one installed but on a machine that is outside of the live
> system. Trying to say we can not use it neither for deployment nor for
> live feed of our side.
Torsten, there is a move to get a better ASF publishing infrastructure.
If we were able to run forrest on minotaur for general use, then we
would have done it long before this. No, we need to wait until other
ASF machines are available, then minotaur can rsync a produced
website from there.
See the current proposal and demo:
http://forrest.apache.org/proposal-asf-publish.html#demo
--David
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2005-03-17 at 11:15 +0100, Torsten Schlabach wrote:
> [Thorsten Scherler wrote:]
> >> We (speaking now officially for forrest) are trying this since ages. We
> >> are not allowed to just go ahead and install things on infrastructure
> >> (like lenya or forrest).
>
> Does that only relate to installing stuff? In other words: Is it allowed
> to use anything which is already installed (such as svn, ant, javadoc) in
> a cron job?
>
> Regards,
> Torsten
>
svn is alright.
ant/javadocs is better you ask on infrastructure and get their ok.
Consider you are working on a public production server and the
performance should not be worse then right now.
HTH
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Torsten Schlabach <ts...@apache.org>.
[Thorsten Scherler wrote:]
>> We (speaking now officially for forrest) are trying this since ages. We
>> are not allowed to just go ahead and install things on infrastructure
>> (like lenya or forrest).
Does that only relate to installing stuff? In other words: Is it allowed
to use anything which is already installed (such as svn, ant, javadoc) in
a cron job?
Regards,
Torsten
> @Gregor I screwed the changes.* links can you deploy the root dir again.
> I am busy atm.
>
> On Sat, 2005-03-05 at 10:55 +0100, Torsten Schlabach wrote:
>> Thorsten,
>>
>> I think you still have the problem with the Apache SSL certificate. Have
>> a look at the log file from this night's run:
>>
>> bash-2.05b@minotaur$ cat /tmp/lenya-site-update.log
>> ===== updating lenya.apache.org website ====
>> Error validating server certificate for 'https://svn.apache.org:443':
>> - The certificate is not issued by a trusted authority. Use the
>> fingerprint to validate the certificate manually!
>> Certificate information:
>> - Hostname: svn.apache.org
>> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
>> - Issuer: http://www.starfieldtech.com/repository, Starfield
>> Technologies, Inc., Scottsdale, Arizona, US
>> - Fingerprint:
>> 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
>> (R)eject, accept (t)emporarily or accept (p)ermanently?
>>
>> If I get it right, the script is asking if you want to accept the
>> certificate, but as the cron job does not have a terminal it just times
>> out and does nothing.
>>
>> A very simple way of fixing this is that you (the user under which the
>> cron job runs) once does
>>
>> cd /www/lenya.apache.org/
>> /usr/local/bin/svn update
>>
>
> I know (I wrote the script). ;-)
>
> They changed the keys and I did not notice that. I have fixed that.
>
>> and interactively permanently accepts the key. This will be put into the
>> SVN settings in your home directory and the script should run run fine
>> in future.
>>
>> One more little thing from your script:
>>
>> >> chmod 777 /tmp/lenya-site-update.log
>>
>> Should a log file be world executable or executable at all?
>>
>
> you are right should only be writable and readable. No need to be
> executable.
>
> Please do
> umask 0002
> before editing something in /www/lenya.apache.org/ or on minotaur
> itself.
>
> I could not change the mod because you are now the owner of the tmp
> file.
>
>> I think this is more of a security hole than it looks like as the file
>> is world writeable. Anyone who breaks in even as user nobody will be
>> able to write whatever code he or she wants into that file and execute
>> it.
>
> Only user have access to minotaur anyway. Any user can execute code in
> their home dir. So not really a big hole. ;-)
>
>> I think especially on a productive server that is as prominent as
>> minotaur we should be a bit more careful. At leats in my very personal
>> opinion. Don't get me wrong.
>>
>
> Like I said ONLY committer have access and their can execute code
> anyway. All user can create a script in e.g. /tmp. Modifying the log
> would be more trouble. ;-)
>
>> >> We have one [Forrestbot] installed but on a machine that is outside
>> >> of the live system. Trying to say we can not use it neither for
>> >> deployment nor for live feed of our side.
>>
>> The original questions was: Is there something or someone that would
>> speak against installing an incarnation of forrest onto minotaur? I mean
>> anyone of us could easily do this in his home dir, but I don't want to
>> violate any ASF policies. And I don't know their policies on this.
>>
>
> Did you read the thread provided by Gregor?
>
> We (speaking now officially for forrest) are trying this since ages. We
> are not allowed to just go ahead and install things on infrastructure
> (like lenya or forrest).
>
> You need to talk to infrastructure about this. Again, I already said, we
> already did that without major success. Go ahead an subscribe to i@a and
> ask for it yourself.
>
> If you go ahead and install lenya or forrest in your home dir without
> prior agreement of infrastructure you are indeed violating ASF policies.
>
> salu2
> --
> thorsten
>
> "Together we stand, divided we fall!"
> Hey you (Pink Floyd)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Thorsten Scherler wrote:
> --> You (or somebody else) already did it in svn.
true. the only thing that needs to be done is recreate the navigation
that has changes.html in it
> I am using 0.7-dev for deployment ATM.
i am using 0.6 for now. i am not sure whether it is a good idea to
switch to non-released forrest versions for building the site. we had
this situation in the past, and it had problems all the time.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Thorsten Scherler <th...@apache.org>.
On Mon, 2005-03-07 at 17:07 -0500, Gregor J. Rothfuss wrote:
> Thorsten Scherler wrote:
> > @Gregor I screwed the changes.* links can you deploy the root dir again.
> > I am busy atm.
>
> please don't comment out changes.html in site.xml. i am not the only one
> who can build it..
Yeah, sorry did not had the time to set up the environment. I fixed.
will be up around 8 h.
"Generating changes.html
changes.html can be directly generated from the SVN commit logs with the
following procedure:
* install Saxon 8 (the svn2changes stylesheet requires a XSLT 2.0
processor)
* run svn log -v --xml http://svn.apache.org/repos/asf/lenya >
log.xml in the root of the docu branch. This might take a while
as the log file is several MB in size.
* run java -jar saxon8.jar -o status.xml log.xml
tools/svn2changes.xsl
* run forest (You may have to increase forrest.maxmemory in
forrest.properties to get around out of memory exceptions.)
Forrest will take a LONG TIME to generate changes.html.
--> You (or somebody else) already did it in svn.
If everything went alright, you will find changes.html, changes.pdf and
changes.rss inside your xdocs directory."
Hmm, I think we should have a look how we can do parts of this process
with
On Mon, 2005-03-07 at 11:41 +0000, Ross Gardler wrote:
> There is now a org.apache.forrest.plugins.projectInfo that handles
> the
> status stuff. The stylesheets and related xmaps have moved there.
I am using 0.7-dev for deployment ATM.
The only thing that fails is the icon. :\
Will have a look on the plugin how we can integrate it.
> will take a look at it tonight.
>
I fixed it already.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Thorsten Scherler wrote:
> @Gregor I screwed the changes.* links can you deploy the root dir again.
> I am busy atm.
please don't comment out changes.html in site.xml. i am not the only one
who can build it..
will take a look at it tonight.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Torsten Schlabach <ts...@apache.org>.
Thorsten,
>> I could not change the mod because you are now the owner of the tmp
>> file.
I have just deleted it, so it will be created again by the next run of
the cron job with the cron job owner as the owner.
>> Did you read the thread provided by Gregor?
I might have overlooked some part of it, but I just remember this beeing
a discussion about the status of a Forrestbot on a non productive
server. This did not answer my question if we can install Forrest on
minotaur, but you've answered it very clearly now. Sorry if I had
overlook an earlier clarification.
>> You need to talk to infrastructure about this. Again, I already said,
>> we already did that without major success. Go ahead an subscribe to
>> i@a and ask for it yourself.
If you did not succeed, why do you think it will make any difference if
I ask?
>> If you go ahead and install lenya or forrest in your home dir without
>> prior agreement of infrastructure you are indeed violating ASF
>> policies.
I don't want that!
Ok, back to square #1.
Regards,
Torsten
Thorsten Scherler schrieb:
> @Gregor I screwed the changes.* links can you deploy the root dir again.
> I am busy atm.
>
> On Sat, 2005-03-05 at 10:55 +0100, Torsten Schlabach wrote:
>
>>Thorsten,
>>
>>I think you still have the problem with the Apache SSL certificate. Have
>>a look at the log file from this night's run:
>>
>>bash-2.05b@minotaur$ cat /tmp/lenya-site-update.log
>> ===== updating lenya.apache.org website ====
>>Error validating server certificate for 'https://svn.apache.org:443':
>> - The certificate is not issued by a trusted authority. Use the
>> fingerprint to validate the certificate manually!
>>Certificate information:
>> - Hostname: svn.apache.org
>> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
>> - Issuer: http://www.starfieldtech.com/repository, Starfield
>>Technologies, Inc., Scottsdale, Arizona, US
>> - Fingerprint: 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
>>(R)eject, accept (t)emporarily or accept (p)ermanently?
>>
>>If I get it right, the script is asking if you want to accept the
>>certificate, but as the cron job does not have a terminal it just times
>>out and does nothing.
>>
>>A very simple way of fixing this is that you (the user under which the
>>cron job runs) once does
>>
>>cd /www/lenya.apache.org/
>>/usr/local/bin/svn update
>>
>
>
> I know (I wrote the script). ;-)
>
> They changed the keys and I did not notice that. I have fixed that.
>
>
>>and interactively permanently accepts the key. This will be put into the
>>SVN settings in your home directory and the script should run run fine
>>in future.
>>
>>One more little thing from your script:
>>
>> >> chmod 777 /tmp/lenya-site-update.log
>>
>>Should a log file be world executable or executable at all?
>>
>
>
> you are right should only be writable and readable. No need to be
> executable.
>
> Please do
> umask 0002
> before editing something in /www/lenya.apache.org/ or on minotaur
> itself.
>
> I could not change the mod because you are now the owner of the tmp
> file.
>
>
>>I think this is more of a security hole than it looks like as the file
>>is world writeable. Anyone who breaks in even as user nobody will be
>>able to write whatever code he or she wants into that file and execute
>>it.
>
>
> Only user have access to minotaur anyway. Any user can execute code in
> their home dir. So not really a big hole. ;-)
>
>
>>I think especially on a productive server that is as prominent as
>>minotaur we should be a bit more careful. At leats in my very personal
>>opinion. Don't get me wrong.
>>
>
>
> Like I said ONLY committer have access and their can execute code
> anyway. All user can create a script in e.g. /tmp. Modifying the log
> would be more trouble. ;-)
>
>
>> >> We have one [Forrestbot] installed but on a machine that is outside
>> >> of the live system. Trying to say we can not use it neither for
>> >> deployment nor for live feed of our side.
>>
>>The original questions was: Is there something or someone that would
>>speak against installing an incarnation of forrest onto minotaur? I mean
>>anyone of us could easily do this in his home dir, but I don't want to
>>violate any ASF policies. And I don't know their policies on this.
>>
>
>
> Did you read the thread provided by Gregor?
>
> We (speaking now officially for forrest) are trying this since ages. We
> are not allowed to just go ahead and install things on infrastructure
> (like lenya or forrest).
>
> You need to talk to infrastructure about this. Again, I already said, we
> already did that without major success. Go ahead an subscribe to i@a and
> ask for it yourself.
>
> If you go ahead and install lenya or forrest in your home dir without
> prior agreement of infrastructure you are indeed violating ASF policies.
>
> salu2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Thorsten Scherler <th...@apache.org>.
@Gregor I screwed the changes.* links can you deploy the root dir again.
I am busy atm.
On Sat, 2005-03-05 at 10:55 +0100, Torsten Schlabach wrote:
> Thorsten,
>
> I think you still have the problem with the Apache SSL certificate. Have
> a look at the log file from this night's run:
>
> bash-2.05b@minotaur$ cat /tmp/lenya-site-update.log
> ===== updating lenya.apache.org website ====
> Error validating server certificate for 'https://svn.apache.org:443':
> - The certificate is not issued by a trusted authority. Use the
> fingerprint to validate the certificate manually!
> Certificate information:
> - Hostname: svn.apache.org
> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
> - Issuer: http://www.starfieldtech.com/repository, Starfield
> Technologies, Inc., Scottsdale, Arizona, US
> - Fingerprint: 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
> (R)eject, accept (t)emporarily or accept (p)ermanently?
>
> If I get it right, the script is asking if you want to accept the
> certificate, but as the cron job does not have a terminal it just times
> out and does nothing.
>
> A very simple way of fixing this is that you (the user under which the
> cron job runs) once does
>
> cd /www/lenya.apache.org/
> /usr/local/bin/svn update
>
I know (I wrote the script). ;-)
They changed the keys and I did not notice that. I have fixed that.
> and interactively permanently accepts the key. This will be put into the
> SVN settings in your home directory and the script should run run fine
> in future.
>
> One more little thing from your script:
>
> >> chmod 777 /tmp/lenya-site-update.log
>
> Should a log file be world executable or executable at all?
>
you are right should only be writable and readable. No need to be
executable.
Please do
umask 0002
before editing something in /www/lenya.apache.org/ or on minotaur
itself.
I could not change the mod because you are now the owner of the tmp
file.
> I think this is more of a security hole than it looks like as the file
> is world writeable. Anyone who breaks in even as user nobody will be
> able to write whatever code he or she wants into that file and execute
> it.
Only user have access to minotaur anyway. Any user can execute code in
their home dir. So not really a big hole. ;-)
> I think especially on a productive server that is as prominent as
> minotaur we should be a bit more careful. At leats in my very personal
> opinion. Don't get me wrong.
>
Like I said ONLY committer have access and their can execute code
anyway. All user can create a script in e.g. /tmp. Modifying the log
would be more trouble. ;-)
> >> We have one [Forrestbot] installed but on a machine that is outside
> >> of the live system. Trying to say we can not use it neither for
> >> deployment nor for live feed of our side.
>
> The original questions was: Is there something or someone that would
> speak against installing an incarnation of forrest onto minotaur? I mean
> anyone of us could easily do this in his home dir, but I don't want to
> violate any ASF policies. And I don't know their policies on this.
>
Did you read the thread provided by Gregor?
We (speaking now officially for forrest) are trying this since ages. We
are not allowed to just go ahead and install things on infrastructure
(like lenya or forrest).
You need to talk to infrastructure about this. Again, I already said, we
already did that without major success. Go ahead an subscribe to i@a and
ask for it yourself.
If you go ahead and install lenya or forrest in your home dir without
prior agreement of infrastructure you are indeed violating ASF policies.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Torsten Schlabach <ts...@apache.org>.
Thorsten,
I think you still have the problem with the Apache SSL certificate. Have
a look at the log file from this night's run:
bash-2.05b@minotaur$ cat /tmp/lenya-site-update.log
===== updating lenya.apache.org website ====
Error validating server certificate for 'https://svn.apache.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.apache.org
- Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
- Issuer: http://www.starfieldtech.com/repository, Starfield
Technologies, Inc., Scottsdale, Arizona, US
- Fingerprint: 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
(R)eject, accept (t)emporarily or accept (p)ermanently?
If I get it right, the script is asking if you want to accept the
certificate, but as the cron job does not have a terminal it just times
out and does nothing.
A very simple way of fixing this is that you (the user under which the
cron job runs) once does
cd /www/lenya.apache.org/
/usr/local/bin/svn update
and interactively permanently accepts the key. This will be put into the
SVN settings in your home directory and the script should run run fine
in future.
One more little thing from your script:
>> chmod 777 /tmp/lenya-site-update.log
Should a log file be world executable or executable at all?
I think this is more of a security hole than it looks like as the file
is world writeable. Anyone who breaks in even as user nobody will be
able to write whatever code he or she wants into that file and execute
it. I think especially on a productive server that is as prominent as
minotaur we should be a bit more careful. At leats in my very personal
opinion. Don't get me wrong.
>> We have one [Forrestbot] installed but on a machine that is outside
>> of the live system. Trying to say we can not use it neither for
>> deployment nor for live feed of our side.
The original questions was: Is there something or someone that would
speak against installing an incarnation of forrest onto minotaur? I mean
anyone of us could easily do this in his home dir, but I don't want to
violate any ASF policies. And I don't know their policies on this.
Regards,
Torsten
Thorsten Scherler schrieb:
> NOTE: CC to forrest-dev because of point 2 from T. Schlabach.
>
> On Fri, 2005-03-04 at 20:18 +0100, Torsten Schlabach wrote:
>
>>Dear all,
>>
>>there are still two issues which I am concerned with:
>>
>>1. The cron job to update minotaur:/www/lenya.apache.org/ with
>>svn.apache.org:/repos/asf/lenya/site seems to to run any more on a
>>regular basis.
>>
>>@Thorsten as the owner of that cron job: Is this by purpose, for any
>>known reason or should we consider this a problem. If we consider it a
>>problem, what can we do to fix this?
>>
>
>
> I fix that (I hope). ;-) We need to keep an eye on it.
>
> It was not on purpose. Thx for the heads up. I think I never activated
> the cron job. ;-)
>
> You will find now thorsten.ct in my home dir:
> ##########################
> # run five minutes after midnight, every day
> 5 0 * * * /x1/home/thorsten/bin/lenya-update.sh
> ##########################
>
> FYI http://www.primenetwork.net/support/cron-job-howto.html
>
>
>
>>2. I has asked this before but got no answer: Is anyone positive that
>>ASF would object to install forrst on minotaur and generate the /site
>>from /docu automatically or on demand, but server-based?
>>
>
>
> We have one installed but on a machine that is outside of the live
> system. Trying to say we can not use it neither for deployment nor for
> live feed of our side.
>
> salu2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Thorsten Scherler <th...@apache.org>.
NOTE: CC to forrest-dev because of point 2 from T. Schlabach.
On Fri, 2005-03-04 at 20:18 +0100, Torsten Schlabach wrote:
> Dear all,
>
> there are still two issues which I am concerned with:
>
> 1. The cron job to update minotaur:/www/lenya.apache.org/ with
> svn.apache.org:/repos/asf/lenya/site seems to to run any more on a
> regular basis.
>
> @Thorsten as the owner of that cron job: Is this by purpose, for any
> known reason or should we consider this a problem. If we consider it a
> problem, what can we do to fix this?
>
I fix that (I hope). ;-) We need to keep an eye on it.
It was not on purpose. Thx for the heads up. I think I never activated
the cron job. ;-)
You will find now thorsten.ct in my home dir:
##########################
# run five minutes after midnight, every day
5 0 * * * /x1/home/thorsten/bin/lenya-update.sh
##########################
FYI http://www.primenetwork.net/support/cron-job-howto.html
> 2. I has asked this before but got no answer: Is anyone positive that
> ASF would object to install forrst on minotaur and generate the /site
> from /docu automatically or on demand, but server-based?
>
We have one installed but on a machine that is outside of the live
system. Trying to say we can not use it neither for deployment nor for
live feed of our side.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: Maintainance of the Lenya Website (lenya.apache.org) again
Posted by Thorsten Scherler <th...@apache.org>.
NOTE: CC to forrest-dev because of point 2 from T. Schlabach.
On Fri, 2005-03-04 at 20:18 +0100, Torsten Schlabach wrote:
> Dear all,
>
> there are still two issues which I am concerned with:
>
> 1. The cron job to update minotaur:/www/lenya.apache.org/ with
> svn.apache.org:/repos/asf/lenya/site seems to to run any more on a
> regular basis.
>
> @Thorsten as the owner of that cron job: Is this by purpose, for any
> known reason or should we consider this a problem. If we consider it a
> problem, what can we do to fix this?
>
I fix that (I hope). ;-) We need to keep an eye on it.
It was not on purpose. Thx for the heads up. I think I never activated
the cron job. ;-)
You will find now thorsten.ct in my home dir:
##########################
# run five minutes after midnight, every day
5 0 * * * /x1/home/thorsten/bin/lenya-update.sh
##########################
FYI http://www.primenetwork.net/support/cron-job-howto.html
> 2. I has asked this before but got no answer: Is anyone positive that
> ASF would object to install forrst on minotaur and generate the /site
> from /docu automatically or on demand, but server-based?
>
We have one installed but on a machine that is outside of the live
system. Trying to say we can not use it neither for deployment nor for
live feed of our side.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org