Access controls for Pages on gitlab.com
Problem to solve
The ability to set up access control for pages was introduced in https://gitlab.com/gitlab-org/gitlab-ce/issues/33422.
There is now an infrastructure ticket to enable it in production: gitlab-com/gl-infra/infrastructure#5576 (closed). This issue represents the engineering team's work to work with the infrastructure team to ensure that happens.
- check what happens when you disable access control(@vshushlin: 404 for me locally, which is strange)
This is a great, working feature that would be valuable to users on gitlab.com as well. We need to ensure that the solution will work and be performant/not cause other issues on gitlab.com before enabling it.
Complete infrastructure ticket and enable feature on gitlab.com.
Links / references
- Infrastructure ticket: gitlab-com/gl-infra/infrastructure#5576 (closed).
- GitLab Pages access control was introduced in https://gitlab.com/gitlab-org/gitlab-ce/issues/33422.
- Here's the Omnibus changes omnibus-gitlab!2583 (merged) and the admin docs are at https://docs.gitlab.com/ee/administration/pages/#access-control.