Actually, this setup works. We use the Same for StormCrawler right now :-) The staging section in the yaml is only on the asf-staging branch.
Am 3. Mai 2025 00:15:45 MESZ schrieb sebb <seb...@gmail.com>: >On Fri, 2 May 2025 at 19:58, Richard Zowalla <r...@apache.org> wrote: >> >> Hi all, >> >> I have updated our Storm website to be build automatically via GitHub >> actions on push to "main". >> >> You have the possbility to either push to "main" and wait for a deploy >> _or_ you create a branch in the site repo and do a staging deploy via a >> manually triggered action. The website is than available via >> https://storm.staged.apache.org/ > >I think you will need to update .asf.yaml to add a staging: section >for that to happen: >https://github.com/apache/infrastructure-asfyaml/?tab=readme-ov-file#staging-a-web-site-preview-domain > >Note that this will not work without a whoami that matches the branch, >see second NOTE here: >https://github.com/apache/infrastructure-asfyaml/?tab=readme-ov-file#web-site-deployment-service-for-git-repositories > >If you wish to have multiple previews then each branch will need a >different profile. > >> That should make it easier to deal with the website (no need to install >> ruby and stuff on your local machine ...) >> >> Gruß >> Richard >>
