You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by Chris Lalancette <cl...@redhat.com> on 2011/06/23 22:53:58 UTC
[PATCH]: Add libdeltacloud documentation to the website
You might notice that there is no patch actually attached ;). That's because
I imported the full doxygen generated documentation, which ends up making
the patch very large (1.3MB). Instead, I've uploaded the patch here:
http://people.redhat.com/clalance/deltacloud-site-libdeltacloud.patch
Note that it is a binary patch, so you'll have to apply with git-am or
git-apply (just patch won't work).
As a side note: is there any reason why we have the site/output directory
checked into the repository? It would seem to me that we only want to have
the sources there, and then just generate the output when we want to push it.
--
Chris Lalancette
Re: [PATCH]: Add libdeltacloud documentation to the website
Posted by Chris Lalancette <cl...@redhat.com>.
On 06/29/11 - 05:18:11PM, David Lutterkort wrote:
> On Thu, 2011-06-23 at 16:53 -0400, Chris Lalancette wrote:
> > As a side note: is there any reason why we have the site/output directory
> > checked into the repository? It would seem to me that we only want to have
> > the sources there, and then just generate the output when we want to push it.
>
> The reason we have output checked in is that that's how you deploy the
> website; it seems to be standard at the ASF, though I agree it's
> strange.
>
> The way the website is updated is by checking things into output/ (e.g.
> by reruning webby)
>
> Then log in to minotaur.apache.org and do an svn up
> in /www/incubator.apache.org/deltacloud - that directory is a checkout
> of
> http://svn.apache.org/repos/asf/incubator/deltacloud/trunk/site/output
>
> If somebody wants to come up with a better way to publish the site, I am
> all for it. But IIRC, doing it via svn is the recommended way.
Ah, I see. If this is the recommended way, then so be it. I'm not all that
upset about it, I just thought it was a little odd :).
--
Chris Lalancette
Re: [PATCH]: Add libdeltacloud documentation to the website
Posted by Michal Fojtik <mf...@redhat.com>.
On Jun 29, 2011, at 5:18 PM, David Lutterkort wrote:
> On Thu, 2011-06-23 at 16:53 -0400, Chris Lalancette wrote:
>> As a side note: is there any reason why we have the site/output directory
>> checked into the repository? It would seem to me that we only want to have
>> the sources there, and then just generate the output when we want to push it.
>
> The reason we have output checked in is that that's how you deploy the
> website; it seems to be standard at the ASF, though I agree it's
> strange.
>
> The way the website is updated is by checking things into output/ (e.g.
> by reruning webby)
>
> Then log in to minotaur.apache.org and do an svn up
> in /www/incubator.apache.org/deltacloud - that directory is a checkout
> of
> http://svn.apache.org/repos/asf/incubator/deltacloud/trunk/site/output
>
> If somebody wants to come up with a better way to publish the site, I am
> all for it. But IIRC, doing it via svn is the recommended way.
Couldn't we setup some GIT post-commit hook that will check if you've commited
something into the site directory and then login to minotaur and do svn up there?
(I'm not sure how to check if the current commit touched the site/)
-- Michal
------------------------------------------------------
Michal Fojtik, mfojtik@redhat.com
Deltacloud API: http://deltacloud.org
Re: [PATCH]: Add libdeltacloud documentation to the website
Posted by David Lutterkort <lu...@redhat.com>.
On Thu, 2011-06-23 at 16:53 -0400, Chris Lalancette wrote:
> As a side note: is there any reason why we have the site/output directory
> checked into the repository? It would seem to me that we only want to have
> the sources there, and then just generate the output when we want to push it.
The reason we have output checked in is that that's how you deploy the
website; it seems to be standard at the ASF, though I agree it's
strange.
The way the website is updated is by checking things into output/ (e.g.
by reruning webby)
Then log in to minotaur.apache.org and do an svn up
in /www/incubator.apache.org/deltacloud - that directory is a checkout
of
http://svn.apache.org/repos/asf/incubator/deltacloud/trunk/site/output
If somebody wants to come up with a better way to publish the site, I am
all for it. But IIRC, doing it via svn is the recommended way.
David
Re: [PATCH]: Add libdeltacloud documentation to the website
Posted by Chris Lalancette <cl...@redhat.com>.
On 06/29/11 - 05:11:45PM, Michal Fojtik wrote:
>
> On Jun 23, 2011, at 10:53 PM, Chris Lalancette wrote:
>
> > You might notice that there is no patch actually attached ;). That's because
> > I imported the full doxygen generated documentation, which ends up making
> > the patch very large (1.3MB). Instead, I've uploaded the patch here:
> >
> > http://people.redhat.com/clalance/deltacloud-site-libdeltacloud.patch
>
> ACK. Thanks for this documentation.
I know it has been a long time, but I finally got around to committing this.
I'll keep an eye on the site in the next hour or so to make sure I didn't
mess anything up.
--
Chris Lalancette
Re: [PATCH]: Add libdeltacloud documentation to the website
Posted by Michal Fojtik <mf...@redhat.com>.
On Jun 23, 2011, at 10:53 PM, Chris Lalancette wrote:
> You might notice that there is no patch actually attached ;). That's because
> I imported the full doxygen generated documentation, which ends up making
> the patch very large (1.3MB). Instead, I've uploaded the patch here:
>
> http://people.redhat.com/clalance/deltacloud-site-libdeltacloud.patch
ACK. Thanks for this documentation.
-- Michal
>
> Note that it is a binary patch, so you'll have to apply with git-am or
> git-apply (just patch won't work).
>
> As a side note: is there any reason why we have the site/output directory
> checked into the repository? It would seem to me that we only want to have
> the sources there, and then just generate the output when we want to push it.
>
> --
> Chris Lalancette
------------------------------------------------------
Michal Fojtik, mfojtik@redhat.com
Deltacloud API: http://deltacloud.org