-
Notifications
You must be signed in to change notification settings - Fork 111
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
hennevogel
wants to merge
12
commits into
master
Choose a base branch
from
staging
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
New Software Portal #1420
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
hennevogel
force-pushed
the
staging
branch
3 times, most recently
from
November 10, 2023 15:28
036c1c7
to
17574ce
Compare
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this we get a (postgres) database with
Distributions
->Repositories
->Packages
->Patches
-Issues
The workflows will be as following:
Distribution
by categoryPackage
of aDistribution
in it'sRepositories
Package
build on OBS for thisDistribution
This has a couple of pro's:
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: