-
Notifications
You must be signed in to change notification settings - Fork 248
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
Repos Update: Draft guides for integration #6061
Repos Update: Draft guides for integration #6061
Conversation
dc98229
to
01db8f7
Compare
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
01a42a1
to
ea24dfe
Compare
``` | ||
|
||
1. Append the appropriate path for the repository type. | ||
For example, for a Red Hat Enterprise Linux 9 on x86 architecture, append `rpm/el/9/x86_64/` and seperately append `rpm/el/9/noarch/` for the noarch packages, to create two base URLs. With our example, the base URLs will be: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a table that enumerates these and also mentions the Debian URLs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would need the details of what is needed to form the Debian URLs in our scheme.
advocacy_docs/repos/working_with_repos/integrating/artifactory.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks correct to me, just two notes that might be worth mentioning; it’s up to you whether you think it’s necessary:
- Explain what it means to create a remote repository with Artifactory (i.e., to proxy the repository).
- Mention that in Artifactory, a virtual repository can also be created to group various remote repositories. For example, you could create a virtual "standard" repository that includes all the "standard" remote repos (x86_64, ppc64le, noarch, etc.). This would simplify the local repository installation. However, it would need to be tested since I don’t remember the exact steps.
5abb458
to
4c5abba
Compare
4c5abba
to
86d2437
Compare
86d2437
to
b7dbee0
Compare
b7dbee0
to
edfc0b2
Compare
edfc0b2
to
8e22e2a
Compare
Signed-off-by: Dj Walker-Morgan <[email protected]>
Signed-off-by: Dj Walker-Morgan <[email protected]>
Signed-off-by: Dj Walker-Morgan <[email protected]>
8e22e2a
to
db89a75
Compare
Edits to Repos Update: Draft guides for integration #6061
What Changed?
Added Artifactory guide