Failing Website Build

[zicklag]

https://github.com/RAUI-labs/raui/blob/8f765a2a8439822440a0b0be809ca97d49818b76/.github/workflows/website.yml#L33

The build is failing for the website and a quick look at the GitHub action, says that you have to create a personal access token and add it to your secrets to allow the site to deploy:

[PsichiX]

ah, that's why! lemme make that one

[zicklag]

You should be able to re-run the build after setting the secret with this button when viewing the failed build.

[PsichiX]

hmm, is there an article about how to properly setup created secret to work with given repo? i'm having problems with the setup after i've created personal secret by following links in Zola readme 🤔

[zicklag]

Not that I know of. :thinking:

I think that you have to creat the token, and then go to the repo settings and add the token as a secret like this:

Also, we'll need to update the URL in the zola config.toml now that the repo org has changed and the URL will be different.

[PsichiX]

great! adding secret to repo and soon will push changes within config.toml

[PsichiX]

https://github.com/RAUI-labs/raui/runs/2570636086

i've ran cargo fmt --all after doing merge of local and remote next branch, but that should format only rust code - could that make this error? 🤔

[zicklag]

Oh, that's weird. I think it's trying to interpret the built zola site as a Jekyll site. We might need to add a .nojekyll file to the site/static folder to make sure that GitHub doesn't try to build the site as a Jekyll site.

[zicklag]

Ah yeah, here's the doc:

[PsichiX]

i think that site/static wasn't the proper place for me to put that file into :D what directory is the "root of publishing source"? 🤔

[zicklag]

It looks like that one worked: https://github.com/RAUI-labs/raui/actions/runs/837008605

[zicklag]

Oh, did you set GitHub pages to use the gh-pages branch to deploy?

[PsichiX]

probably 😅 i'm basically newbie when it comes to zola and GH pages :D

[zicklag]

[zicklag]

That's what you should do.

[zicklag]

probably sweat_smile i'm basically newbie when it comes to zola and GH pages :D

No problem. :D

I'm new to Zola, too.

I think putting .nojekyll in the static did work, we just need to make sure that GitHub pages is using the gh-pages branch and not the master branch to deploy.

[PsichiX]

ok, so i've changed pages branch to gh-pages, also in last commit i've moved .nojekyll to site/.nojekyll but i don't see that change failed zola build so i think it can stay there.

i believe that i should re-run zola build again to make GH pages use gh-pages branch after change?

[PsichiX]

hmm, no, something is wrong again xD ok, i'll move back .nojekyll to static and re-run all jobs

[zicklag]

I think that will work. :)

[PsichiX]

YAY, we're live! :D :D :D

[zicklag]

It worked!!!! 🤯

Yay!

[PsichiX]

thanks for your great help with it <3

[zicklag]

Now we just need to update the repo link!

[PsichiX]

where? :O i thought i've fixed URLs in all places :O

[zicklag]

Glad I could help! It was good experience and I learned quite a bit from it. :)

[zicklag]

Just the one that pops up here:

The one that you set from the repo description.

[zicklag]

[PsichiX]

changed and added tags :D

[zicklag]

Perfect!