Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Software Portal #1420

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

New Software Portal #1420

wants to merge 12 commits into from

Conversation

hennevogel
Copy link
Member

With this we get a (postgres) database with Distributions -> Repositories -> Packages -> Patches - Issues

The workflows will be as following:

  • As an admin I setup Distribution and it's repositories
  • As an admin I sync all repositories repomd files into to the database
  • As a user I browse a Distribution by category
  • As a user I search for Package of a Distribution in it's Repositories
  • As a user I extend the search to Package build on OBS for this Distribution

This has a couple of pro's:

  • Less traffic on the OBS API as the usual Packages are inside the database
  • Easier base to add features to this page. Like comments, ratings, openSUSE specific screenshots etc.
  • Separating the Distribution package search from searching through OBS will hopefully make more clear for newbies that enabling extra repositories is kind of dangerous.

And one con:

  • You can't search for packages build for foreign distributions with this app anymore (although we could consume their repomd etc. but I doubt we have the audience on an opensuse.org domain...)

Also moves docker base image build into OBS
All the stuff we need for what's to come...
A Distribution has many Repository
A Repository has many Packages
A Package has many Versions
A Package has many Categories

ActiveJobs are in the database too.
With this we get a Distribution with a bunch of Repository in the database that
you can sync. Which will create, per Distribution/Repository, a gazillion
Package objects with data from primary, appdata and updateinfo.

The user workflow will be as following:

- As an admin I setup Distribution and it's repositories
- As an admin I sync a Distribution's repositories to the database

- As a user I search for Package of a Distributions in it's repositories
- As a user I extend the search to packages build on OBS for this Distribution (not implemented here)

Separating the Distribution "repository" search from searching through OBS will
hopefully make more clear for newbies that enabling extra repos is kind of
dangerous.
and regenerate TODO file...
Using dentarg/postgres
For debugging production...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant