openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Rutkowski" <>
Subject Re: [Admin] Site
Date Wed, 14 Dec 2016 15:37:25 GMT
In regard, to # 3

What is the benefit of hosting a static HTML site (which would have to be 
created) versus pursuing hosting of the javascript (static HTML 
generation) site we already have in the OpenWhisk project (i.e., which has been updated 
for Apache (e.g., logoing and content)?  It would seem all we would need 
is something to host the JS server (packaged perhaps in some container)?

Kind regards,

From:   Felix Meschberger <>
To:     "" 
Date:   12/14/2016 07:19 AM
Subject:        Re: [Admin] Site


That sounds great. So we have:

(1) developer updates the site, commits to site-repo/master
(2) Jenkins Site build triggered from push
(3) Static HTML of site pushed to site-repo/asf-site
(4) gitpubsub kicks in an publishes the site

For the time being, I think we can still do steps (2) and (3) manually but 
would get the automatically pushed site rather quickly.

This is probably again a question for Greg: Can we set this up even now in 
the short term before even having transferred the Git repositories ?


> Am 13.12.2016 um 20:47 schrieb Greg Stein <>:
> On Mon, Dec 12, 2016 at 05:45:37PM +0100, Bertrand Delacretaz wrote:
>> Hi Felix,
>> On Mon, Dec 12, 2016 at 4:03 PM, Felix Meschberger <> 
>>> ...The question is, how are we going to setup the „automatic“ or 
controlled publication...
>> As per [1] it's possible to publish ASF websites from Git.
> Yup. And it is quite easy to have a Jenkins/buildbot job run once a
> commit is made to the source, which transforms that source into HTML
> and commits it. Via gitpubsub, the committed HTML gets published on
> the website.
> Cheers,
> -g

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message