-
Notifications
You must be signed in to change notification settings - Fork 168
Conversation
Both PyPI and source ones. closes #4356 https://pulp.plan.io/issues/4356
|
||
$ pulp-manager runserver |
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.
Changed to pulp-manager
for consistency here (since it's used in all the other instructions above).
Codecov Report
@@ Coverage Diff @@
## master #3865 +/- ##
=======================================
Coverage 55.79% 55.79%
=======================================
Files 66 66
Lines 2848 2848
=======================================
Hits 1589 1589
Misses 1259 1259 Continue to review full report at Codecov.
|
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.
LGTM
@@ -43,20 +43,19 @@ PyPI Installation | |||
|
|||
$ sudo apt-get install python3-venv | |||
|
|||
3. Install Pulp:: | |||
3. Install Pulp (install ``pulpcore-plugin``, and ``pulpcore`` itself will be installed as | |||
a dependency):: |
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.
Maybe we should suggest that the user install the plugin they want, and pulpcore-plugin will be picked up as a dep. Is there any reason a user would install pulp without a plugin?
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.
That makes sense to me. Something like:
3. Installing a plugin will automatically install ``pulpcore`` and ``pulpcore-plugin``::
pip install pulp_file
Or you can install the individual packages of ``pulpcore`` and ``pulpcore-plugin``:
pip install pulpcore pulpcore-plugin
Both PyPI and source ones.
closes #4356
https://pulp.plan.io/issues/4356