CI deployment

[Kumzy]

Litestar website

Add CI to deploy website

I would like to add a CI to this project that would deploy the website in the static pages, I created a deploy.yml file but as the project is private, I guess there is no pages.

Add CI to pull plugins data on building website

The repo of plugins: http://github.com/litestar-org/plugins

I would like to have a CI on this project to pull data from the plugins repository. I do not know what is the best way to do it. I thought about that
In the plugin, create artifacts with data (json and yml files) and on build of this website, we pull these artifacts
Commands to run on the plugin project to generate files

uv run sync
uv run get-readme

Add CI to update the stats of the website every week

Create a task that will build the website and deploy it every week (depending on the option used before)
It must pull data from the plugins repository first

Add CI to pull data from plugins (running plugins scripts) after a Litestar release

After a new release of Litestar, we have to rebuild the website to update the version of Litestar

Plugin repository

That's for the plugin repository: http://github.com/litestar-org/plugins

Create CI that will run the scripts (plugins+stats) after a successful merged PR on main

When a PR is merged successfully on the plugin repository, I would like to run the scripts to update the stats and generate the artifacts

Create CI that will run the scripts every week to update data (artifacts)

I would like to create an action that will run every week to update the stats of the plugins (gh stars, download, etc)
So when we build the website everyweek, we can have the latest stats

@JacobCoffee

[JacobCoffee]

@Kumzy im coming back to being in the same spot for more than 24 hours.. did you finish this from that preview link you sent us or is there still things needing done?

[Kumzy]

@JacobCoffee I need to do the part with the plugins update. also I would like to know if this is the best way to update data