Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions guides/common/assembly_importing-content.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,12 @@ include::modules/proc_uploading-content-to-custom-rpm-repositories-by-using-web-

include::modules/proc_uploading-content-to-custom-rpm-repositories-by-using-cli.adoc[leveloffset=+1]

ifndef::satellite[]
include::modules/proc_uploading-content-to-deb-repositories-by-using-web-ui.adoc[leveloffset=+1]

include::modules/proc_uploading-content-to-deb-repositories-by-using-cli.adoc[leveloffset=+1]
endif::[]

include::modules/proc_refreshing-content-counts-on-smart-proxy.adoc[leveloffset=+1]

include::modules/proc_configuring-selinux-to-permit-content-synchronization-on-custom-ports.adoc[leveloffset=+1]
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
:_mod-docs-content-type: PROCEDURE

[id="uploading-content-to-deb-repositories-by-using-cli"]
= Uploading content to Deb repositories by using Hammer CLI

[role="_abstract"]
You can upload individual Deb packages to Deb repositories by using Hammer CLI.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optional (because we're not there with the other abstracts yet and it wouldn't be fair to require this at the moment): Ideally, an abstract should also clarify the use case: when and why a user might want to follow the procedure, not just what the procedure does.

For example when: Is the "individual packages" part important here? Is this what distinguishes this procedure from other procedures in the guide? When would a user want to upload an individual package?

Or why: What will happen when the package will be uploaded? Can we explicitly specify that the package will then be available for hosts?

Do not upload packages to a repository if you have set the *Upstream URL*.

.Procedure
* Upload a Deb package:
+
[options="nowrap" subs="+quotes,verbatim"]
----
$ hammer repository upload-content \
--content-type deb \
--id _My_Repository_ID_ \
--path _/path/to/example-package.deb_
----

.Verification
* Verify that your Deb repository contains the Deb package that you have uploaded:
+
[options="nowrap" subs="+quotes,verbatim"]
----
$ hammer deb list --repository-id _My_Repository_ID_
----
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
:_mod-docs-content-type: PROCEDURE

[id="uploading-content-to-deb-repositories-by-using-web-ui"]
= Uploading content to Deb repositories by using {ProjectWebUI}

[role="_abstract"]
You can upload individual Deb packages to Deb repositories by using {ProjectWebUI}.

.Procedure
. In the {ProjectWebUI}, navigate to *Content* > *Products*.
. Select your {customproduct}.
. Select the Deb repository that you want to upload packages to.
Do not upload packages to a repository if you have set the *Upstream URL*.
. Under *Upload Package*, click *Browse...* and select the Deb package that you want to upload.
. Click *Upload*.

.Verification
* To view all Deb packages in this repository, click the number next to *Packages* under *Content Counts*.