ci: scheduled&manual workflow to update bin.walrus.site

[mlegner]

Successful workflow run: https://github.com/MystenLabs/walrus-docs/actions/runs/10006893810/job/27660483590

Closes #64

[giac-mysten]

Thanks @mlegner , looks great! One thing I noticed is that the root page for the site generated by the --list-directory command has the title "Directory listing for /". The "/" is not particularly descriptive, maybe we can use the name of the folder. Opened an issue on walrus sites

[quepcompute]

It's a bit unfortunate that we need a personal access token in the calling workflow
This is is common practice within the Mysten org right now. AFAIK they're being used where workflows touch multiple repositories.

[quepcompute]

      - name: Copy site-builder binary
        run: "cp bin/site-builder site/site-builder-ubuntu-x86_64"

      - name: Update Walrus Site
        run: >
          RUST_LOG=site_builder=debug,walrus=debug,info
          site-builder
          --config walrus-sites/site-builder/assets/builder-example.yaml
          update --list-directory site ${{ vars.WALRUS_SITE_BIN_OBJECT }}

When the devnet workflow is being executed, the jobs for each arch are running in parallel, @mlegner can you confirm that only the ubuntu-x86_64 job needs to call out to this workflow?

[mlegner]

can you confirm that only the ubuntu-x86_64 job needs to call out to this workflow?

Ideally we would call this workflow when all three of the builds succeeded.