Matt, okay, forget about the domain name. Can you help me with setting up gh-pages branch to show up in a page that is not overriding a currently existing one. Any domain name is fine.
On Fri, Oct 15, 2021 at 5:27 PM Matt Sicker <[email protected]> wrote: > I’m not exactly sure how we can get a beta subdomain, though the staging > one is built in. And while it would be great to automate as much as > possible about the release process in GHA, the code signing aspect is still > not possible (though we might be able to integrate with another service at > Apache for that, but it doesn’t cover the GPG signature). There’s also some > ASF rule I think about releases needing to be done by a human, but that > might be more about reproducible builds. > > Matt Sicker > > > On Oct 15, 2021, at 05:57, Volkan Yazıcı <[email protected]> wrote: > > > > I long had the ambition to move the entire site & manual to gh-pages. > > In an ideal world, I would even move the release process to GitHub > Actions > > too. > > But these are, for now, pretty ambitious goals. > > What I would really appreciate is to access gh-pages content via, say, > > https://beta.logging.apache.org/log4j URL. > > Matt, mind helping me with setting this up please? > > > >> On Wed, Oct 13, 2021 at 7:12 PM Matt Sicker <[email protected]> wrote: > >> > >> That's really cool! Do note that we can publish to the ASF-specific > >> branches, too, for hosting a site. > >> > >>> On Wed, Oct 13, 2021 at 10:37 AM Volkan Yazıcı <[email protected]> wrote: > >>> > >>> Do this: > >>> > >>> git fetch -p > >>> git checkout -B gh-pages origin/gh-pages > >>> python -m http.server > >>> open http://localhost:8000/benchmark/results/index.html > >>> > >>> *The magic:* > >>> > >> > https://github.com/apache/logging-log4j2/blob/release-2.x/.github/workflows/benchmark.yml > >>> > >>> *Disadvantages:* Runner specs are on the flux, though mostly pretty > >> stable. > >>> > >>> *Future work:* > >>> > >>> - Enable GitHub pages for the project? > >>> - Incorporate more from log4j-perf to here. > >>> - Put the workflow onto a cron schedule. > >> >
