>> [1] Christian's recent Jekyll experiment on the `asf-staging` branch >> of `logging-site` repository confused the INFRA and it is acting >> strangely. This will *NOT* be an issue when we push the website >> changes to production, i.e., `asf-site` branch. Though we will try >> fixing `asf-staging` anyway in the meantime.
On Fri, Oct 13, 2023, at 13:28, Piotr P. Karwasz wrote: > I think that the problem is that the `asf-staging` branch in > `logging-site` has switched from a `content` folder to an `output` > folder, while some of our 6 other site repos have a `content` folder. > It is fixable, but INFRA offers us an infinite number of > `logging-<foo>.staged.apache.org` domains and I think we should use > it. According to this doc: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories We just have to give it a profile: staging: profile: mystuff Would result in: logging-mystuff.staged.apache.org I can easily migrate to this. The folder "output" is the default with ASF infra, but it is possible to replace it with content: jekyll: whoami: jekyll target: asf-staging outputdir: content Why is content not causing this issue? For me both is possible, just trying to understand the best way. Kind regards, Christian
