You should see my other message but I will reply to your questions also. > On Apr 16, 2021, at 1:37 PM, Gilles Sadowski <gillese...@gmail.com> wrote: > > Hello. > > Le ven. 16 avr. 2021 à 20:39, Ralph Goers <ralph.go...@dslextreme.com> a > écrit : >> >> FYI - I did the work of moving Logging Services site from the CMS to git. It >> really wasn’t that hard. The main web site is at >> https://github.com/apache/logging-site >> <https://github.com/apache/logging-site>. > > So (IIUC this time), we can get things going by requesting/creating a new > "git" repository that would be called "commons-site"?
You could either put everything under commons-site, host just the main site there and put the sub-projects in their own repos, host the main site and some of the sub-projects there with others in their own repos, or almost any other combination you want to dream up. > >> Each of the subproject has their own site such as >> https://github.com/apache/logging-log4j-site >> <https://github.com/apache/logging-log4j-site>. > > Is this an independent "git" repository? > Do we also create those as would be a normal repository? Yes, use the standard tool to create the repos. Infra isn’t involved. > > I see that the log4j "components" are under > https://github.com/apache/logging-site/tree/master/docs/projects > > And there is only one file (".asf.yaml") in > https://github.com/apache/logging-log4j-site The default directory is probably master. Nothing actually happens there. The asf-site branch is where the live site is hosted and the asf-staging branch is where the staging site is hosted. > >> Although the Logging Services site is small the Log4j site is very large. I >> can tell you that publishing the web site for each new releases is order of >> magnitudes faster than SVN was. I did have to modify how the logging >> services site gets built but all the subprojects use the Maven site plugin. > > As noted previously, we seem to use that too in (all?) Commons > components > $ mvn site > > But, how does one go from the web files created in the > target/site/staging > directory, to them being moved (?) to the site repository?[1] When I release Log4j I rum mvn site followed by "mvn site:stage -DstagingDirectory=$HOME/log4j” on my laptop. I validate the site locally and then zip the site, cd to my logging-log4j-site project and unzip it where I want it to go. If you look at https://github.com/apache/logging-log4j-site/tree/asf-staging <https://github.com/apache/logging-log4j-site/tree/asf-staging> you will notice that every release of log4j has its own web site in its own directory. This allows anyone to go and look at any past release of the web site. But if you only want to publish the current version of the site you can just overlay the previous version or set the stagingDirectory location to where the particular site is on your laptop. > > Regards, > Gilles > > [1] The "Manage the Git Hosted Web Site" link on > https://github.com/apache/logging-site > points to > https://cwiki.apache.org/confluence Thanks, I will fix that. Ralph
