>
> Rather than serving the production site from the *content/* directory on
> the master branch, is there any objection to serving it from the asf-site
> branch? This would mean that the last step in the above process would be
> performed on the asf-site branch rather than the master branch. In
>
Hi Murukesh,
That is a good question. To clarify, I meant that if we changed the site to
be serviced from the 'asf-site' branch the master branch would be cleaner
from that point forward.
However, now that you mention it, I do like the idea of cleaning the entire
master branch. Given that this al
For clarification, when you say "this would clean the master
branch history", would the content directory be removed from past commits
using bfg or similar tools?
(I'm fine with either way; just curious.)
On Fri, 1 May 2020, 07:12 Anthony Grasso, wrote:
> Hi everyone,
>
> Thanks to hard work by
Hi everyone,
Thanks to hard work by Mick every push to the cassandra-website *src/*
directory in master is now automatically deployed to
https://cassandra.staged.apache.org/. The automation is carried out by a
Jenkins job at https://ci-cassandra.apache.org/job/cassandra-website/. This
is really us
There's instructions on https://github.com/apache/cassandra-website which I
found out from Mick earlier this week. Cheers!
Thanks Mick, if there documentation somewhere on how we update the website
?
A
-
Aaron Morton
New Zealand
@aaronmorton
CEO
Apache Cassandra Consulting
http://www.thelastpickle.com
On Tue, 21 Apr 2020 at 18:40, Mick Semb Wever wrote:
> For our cassandra-website repository, any
For our cassandra-website repository, any changes to our website can now
first be staged at https://cassandra.staged.apache.org/
The staged website comes from the content/ directory on the `asf-staging`
branch.
regards,
Mick
