4 ms·

Not gp, but: you have a marvelous security system, but GitLab Pages does not use it. For an installation containing private/protected projects, this severely li

by elygre 8y ago

Not gp, but: you have a marvelous security system, but GitLab Pages does not use it. For an installation containing private/protected projects, this severely limits the use of Pages. For example, it is not possible to use Pages to build documentation that should only be available to project members. Everything published to Pages is available to the public.

sytse 8y ago
Thanks! I see you also contributed this as an issue https://gitlab.com/gitlab-org/gitlab-ce/issues/33422 https://gitlab.com/gitlab-org/gitlab-ce/issues/33422 and we plan to make this in the next 4-7 releases. Many of our users have a self-managed installation that is behind the firewall so for them this is less relevant. But we understand the urgency. And of course it would be even quicker if someone can contribute this functionality.
- donmcronald 8y ago
  I've been following that one for a long time. Someone started a contribution for it (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18589 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18589) and there's a GitLab person that appears to be very responsive, so it's going to land eventually. Once that lands, it would be amazing to have a way to leverage CI + pages + auth to provide docs for external users. For years, I've been looking for a way to host authenticated, infrequently used docs. There are no options. Static sites on self-hosted, authenticated GitLab Pages would be perfect if I didn't have to pay for every user.
wyldfire 8y ago
I think it would be a business mistake for them to prioritize this feature over others.
- elygre 8y ago
  Possibly. For our use case (300 users, 900 projects), it makes Pages a non-starter. And the upside would be to move almost all technical documentation from SharePoint to GitLab, which would make the platform significantly more sticky than it is today.

by elygre 8y ago

sytse 8y ago

Thanks! I see you also contributed this as an issue https://gitlab.com/gitlab-org/gitlab-ce/issues/33422 https://gitlab.com/gitlab-org/gitlab-ce/issues/33422 and we plan to make this in the next 4-7 releases. Many of our users have a self-managed installation that is behind the firewall so for them this is less relevant. But we understand the urgency. And of course it would be even quicker if someone can contribute this functionality.

donmcronald 8y ago
I've been following that one for a long time. Someone started a contribution for it (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18589 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18589) and there's a GitLab person that appears to be very responsive, so it's going to land eventually. Once that lands, it would be amazing to have a way to leverage CI + pages + auth to provide docs for external users. For years, I've been looking for a way to host authenticated, infrequently used docs. There are no options. Static sites on self-hosted, authenticated GitLab Pages would be perfect if I didn't have to pay for every user.

wyldfire 8y ago

I think it would be a business mistake for them to prioritize this feature over others.

elygre 8y ago
Possibly. For our use case (300 users, 900 projects), it makes Pages a non-starter. And the upside would be to move almost all technical documentation from SharePoint to GitLab, which would make the platform significantly more sticky than it is today.