search

FreshRSS / Extensions

A repository containing all the official FreshRSS extensions
GNU Affero General Public License v3.0
321 stars 52 forks source link

Feature/automated generation #83

Closed aledeg closed 2 years ago

aledeg commented 4 years ago

Instead of manually maintaining the file, there is now a tool that grab all repositories defined in the repositories.json file and browse through all repositories to find extensions. To do that, I've added a container that runs only php-cli to trigger said tool.

The next step will be to trigger that tool automatically on a regular basis and to update the current repository when there are changes.

Alkarex commented 3 years ago

I somehow did not see this PR until now, sorry! Could you resolve the conflicts?

aledeg commented 3 years ago

I will as soon as I resume my work on that. I'll keep you posted!

Alkarex commented 3 years ago

It would be nice to keep downloaded repositories in a cache to avoid too much resource consumption. And if the cache already exists, then use a a git fetch and git reset instead of git clone.

aledeg commented 3 years ago

It would be nice to keep downloaded repositories in a cache to avoid too much resource consumption. And if the cache already exists, then use a a git fetch and git reset instead of git clone.

I think it would be really hard for no real gain. My goal is to trigger the generation tool once a day automatically with github actions. I am pretty sure I cannot keep cache between executions. The idea is to have the file always up-to-date with a delay of 24 hours maximum and to avoid manual work.

Frenzie commented 3 years ago

With the exception of the two framagit repos, by being on GitHub they're already in cache for all intents and purposes.

@aledeg Is this focus on master and --no-tags correct for all of the extensions? One may well update the json long before tagging a release.

aledeg commented 3 years ago

@Frenzie You're right. Do you have any suggestion on how I could address that? Do we keep a policy in the file description? Do we use a single rule for all repositories?

Frenzie commented 3 years ago

A single rule of tags if there are any, otherwise json might do the trick. But indeed, manual policy is probably better/safer. Not quite sure.

aledeg commented 3 years ago

I'll look into that!

Alkarex commented 2 years ago

A little conflict :-)

aledeg commented 2 years ago

I've solved the conflict. I'll try to find a way to address @Frenzie 's concern about the tagging issue. I have some ideas but I have to dig a little bit.

aledeg commented 2 years ago

I need also to dig into github actions to see how I can build the list automatically. That will be fun, I am looking forward to it.

aledeg commented 2 years ago

Oh! shoot. I was not ready :/ I'll make another branch.

Alkarex commented 2 years ago

Ah, I thought you wanted the CI in another PR :-)

aledeg commented 2 years ago

Don't worry. I'll make the changes in another PR :)