warpstreamlabs / bento

Fancy stream processing made operationally mundane. This repository is a fork of the original project before the license was changed.
https://warpstreamlabs.github.io/bento/
Other
1.07k stars 71 forks source link

website not redeployed #45

Closed jem-davies closed 5 months ago

jem-davies commented 5 months ago

Should the website github action redeploy when there is a succesful push to main?

richardartoul commented 5 months ago

That would be convenient! Feel free to submit a P.R

jem-davies commented 5 months ago

https://github.com/warpstreamlabs/bento/actions/workflows/pages/pages-build-deployment

Where is the definition of this cicd pipeline, should it be in here?

jem-davies commented 5 months ago

looks like you just put them on the branch gh-pages - and there is no deploy site github action file.

jem-davies commented 5 months ago

@epot looks like you did the work on the fork for the deployment of the new docs site?

Is there a github action yaml definition for this already written?

richardartoul commented 5 months ago

I think these commands just need to be run: https://github.com/warpstreamlabs/bento/blob/main/website/README.md

epot commented 5 months ago

I'll double check tomorrow from my laptop but I think it was 'yarn build' and then 'yarn deploy'.

epot commented 5 months ago

Sorry I forgot to circle back here, I confirm those commands above were the ones I ran the one time I updated the doc.