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

portus: documentation is missing lots of information #115

Closed
mssola opened this issue Dec 12, 2018 · 0 comments
Closed

portus: documentation is missing lots of information #115

mssola opened this issue Dec 12, 2018 · 0 comments

Comments

@mssola
Copy link
Contributor

mssola commented Dec 12, 2018

The documentation for portus on SLE is missing a lot of information.

For starters:

Portus is accessible for SLES customers as a Docker image.

This is missing the location where this Docker image can be pulled: the SUSE Container Registry. Portus 2.4 has been released there as a Docker image and it's based on SLE, so customers shouldn't be pulling from Dockerhub, ever. And they should not be looking at the containers module either.

For more information and documentation about Portus, see: http://port.us.org/docs/deploy.html.

This is true, but it's missing quite a lot of info. The difference between the community and the customer-supported version of the Docker image resides only on the base image and how we build said images (the community version is built on Dockerhub, the customer one on IBS). Besides that, there's no real difference: it's the same code. So, setting up the customer-supported version and maintaining it is exactly the same as doing so with the community image. This part of the documentation should be more clear on this because otherwise, customers can get lost.

Moreover, as explained on this page, we also provide some examples on how to deploy Portus here. Maybe it would be worth it to also write this here.

mssola added a commit to mssola/doc-sle that referenced this issue Dec 12, 2018
In particular, I've added a couple of lines that should address some of
the confusions that our customers have reported.

Fixes SUSE/doc-caasp#115

Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
ghost pushed a commit to mssola/doc-sle that referenced this issue Dec 14, 2018
In particular, I've added a couple of lines that should address some of
the confusions that our customers have reported.

Fixes SUSE/doc-caasp#115

Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
@ghost ghost closed this as completed in SUSE/doc-sle#381 Dec 14, 2018
ghost pushed a commit to SUSE/doc-sle that referenced this issue Dec 14, 2018
In particular, I've added a couple of lines that should address some of
the confusions that our customers have reported.

Fixes SUSE/doc-caasp#115

Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
ghost pushed a commit to SUSE/doc-sle that referenced this issue Dec 14, 2018
In particular, I've added a couple of lines that should address some of
the confusions that our customers have reported.

Fixes SUSE/doc-caasp#115

Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
ghost pushed a commit to SUSE/doc-sle that referenced this issue Dec 14, 2018
In particular, I've added a couple of lines that should address some of
the confusions that our customers have reported.

Fixes SUSE/doc-caasp#115

Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
This issue was closed.
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

No branches or pull requests

1 participant