Rename "source installation" to "self-compiled installation" in documentation
Problem to solve
In gitlab-com/support/support-team-meta#3489 (closed) we decided to rename the installations from source to self-compiled installations.
This resulted to the epic &10716, and we documented how to name the methods in https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#how-to-document-different-installation-methods.
This issue is about renaming to the new term in gitlab-org/gitlab
.
Proposal
Replace the following occurrences of source installation
or installation from source
with self-compiled installation
:
doc/security/crime_vulnerability.md:26:- [Source installation NGINX file](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/support/nginx/gitlab-ssl)
doc/raketasks/x509_signatures.md:27:**Source Installations:**
doc/raketasks/backup_gitlab.md:791:- `gitlab_rails['backup_path']` (`backup.path` for source installations).
doc/raketasks/backup_gitlab.md:792:- `gitlab_rails['backup_upload_connection'].local_root` (`backup.upload.connection.local_root` for source installations).
doc/raketasks/spdx.md:18:# source installations
doc/raketasks/web_hooks.md:22:# source installations
doc/raketasks/web_hooks.md:34:# source installations
doc/raketasks/web_hooks.md:46:# source installations
doc/raketasks/web_hooks.md:58:# source installations
doc/raketasks/web_hooks.md:70:# source installations
doc/raketasks/web_hooks.md:82:# source installations
doc/user/admin_area/settings/user_and_ip_rate_limits.md:136: - For source installations, set `export GITLAB_THROTTLE_BYPASS_HEADER=Gitlab-Bypass-Rate-Limiting`
doc/user/admin_area/settings/user_and_ip_rate_limits.md:168:- For source installations, set `export GITLAB_THROTTLE_USER_ALLOWLIST=1,53,217`
doc/user/project/service_desk.md:450:The Microsoft Graph API is not yet supported in source installations.
doc/update/index.md:29:- [Source installations](#installation-from-source)
doc/update/index.md:437: - From source installation default: 50
doc/update/index.md:1080: # For source installations
doc/update/index.md:1216: # For source installations
doc/downgrade_ee_to_ce/index.md:49:- **Source Installation**
doc/downgrade_ee_to_ce/index.md:85:- **Source Installation**
doc/downgrade_ee_to_ce/index.md:87: To downgrade a source installation, you must replace the current remote of
doc/development/workhorse/configuration.md:201:Source installations (`/etc/default/gitlab`):
doc/development/application_secrets.md:41:- [Change for source installation](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/27581)
doc/administration/pages/source.md:7:# GitLab Pages administration for source installations **(FREE SELF)**
doc/administration/pages/index.md:15:[GitLab Pages administration for source installations](source.md).
doc/administration/pages/index.md:916:- Nested under `pages:` and then `object_store:` on source installations.
doc/administration/monitoring/prometheus/gitlab_metrics.md:26:and Chart installations. For source installations, these metrics must be enabled
doc/administration/file_hooks.md:63:- `log/file_hook.log` in a source installation.
doc/administration/raketasks/maintenance.md:22:**Source Installation**
doc/administration/raketasks/maintenance.md:85:**Source Installation**
doc/administration/raketasks/maintenance.md:133:**Source Installation**
doc/administration/raketasks/maintenance.md:199:**Source Installation**
doc/administration/raketasks/maintenance.md:225:**Source Installation**
doc/administration/raketasks/maintenance.md:237:This Rake task only applies to source installations. [Read more](../../update/package/index.md#missing-asset-files)
doc/administration/raketasks/maintenance.md:243:**Source Installation**
doc/administration/raketasks/maintenance.md:270:**Source Installation**
doc/administration/raketasks/smtp.md:27:**Source Installation**
doc/administration/raketasks/smtp.md:50:**Source Installation**
doc/administration/raketasks/smtp.md:66:**Source Installation**
doc/administration/raketasks/uploads/migrate.md:39:**Source Installation**
doc/administration/raketasks/uploads/migrate.md:123:**Source Installation**
doc/administration/raketasks/uploads/migrate.md:181:**Source installation**
doc/administration/raketasks/check.md:51:**Source Installation**
doc/administration/raketasks/check.md:82:**Source Installation**
doc/administration/raketasks/check.md:134:**Source Installation**
doc/administration/raketasks/check.md:225:**Source Installation**
doc/administration/raketasks/check.md:256:**Source Installation**
doc/administration/raketasks/praefect.md:27:**Source Installation**
doc/administration/raketasks/ldap.md:24:**Source Installation**
doc/administration/raketasks/ldap.md:56:**Source Installation**
doc/administration/raketasks/ldap.md:95:**Source Installation**
doc/administration/raketasks/ldap.md:132:**Source Installation**
doc/administration/raketasks/ldap.md:167:**Source Installation**
doc/administration/raketasks/ldap.md:191:**Source Installation**
doc/administration/raketasks/ldap.md:207:**Source Installation**
doc/administration/raketasks/geo.md:27:**Source Installation**
doc/administration/raketasks/geo.md:45:**Source Installation**
doc/administration/raketasks/geo.md:62:**Source Installation**
doc/administration/raketasks/geo.md:79:**Source Installation**
doc/administration/raketasks/storage.md:35:- **Source installation**
doc/administration/raketasks/storage.md:63:- **Source installation**
doc/administration/raketasks/storage.md:95:- **Source installation**
doc/administration/raketasks/storage.md:147:- **Source installation**
doc/administration/incoming_email.md:868:The Microsoft Graph API is not yet supported in source installations. See [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/326169) for more details.
doc/administration/repository_storage_paths.md:81:Omnibus GitLab takes care of these issues for you, but for source installations you should be extra
doc/administration/repository_storage_paths.md:90:the parent path, but source installations do not.
doc/administration/postgresql/multiple_databases.md:44:### Existing source installation
doc/administration/auth/crowd.md:80:1. [Reconfigure](../restart_gitlab.md#omnibus-gitlab-reconfigure) (Omnibus GitLab) or [restart](../restart_gitlab.md#installations-from-source) (source installations) for
doc/administration/cicd.md:17:- `gitlab.yml` for source installations.
doc/administration/operations/puma.md:333:For source installations, set the environment variable.
doc/administration/sidekiq/sidekiq_job_migration.md:41:# source installations
doc/administration/uploads.md:71:For source installations the following settings are nested under `uploads:` and then `object_store:`. On Omnibus GitLab installs they are prefixed by `uploads_object_store_`.
doc/administration/gitaly/configure_gitaly.md:44:- The GitLab [source installation guide](../../install/installation.md).
doc/administration/gitaly/index.md:171:- Source installations or custom Gitaly installations, see [Configure Gitaly](configure_gitaly.md).
doc/administration/user_settings.md:33:**Source installations**
doc/administration/user_settings.md:65:**Source installations**
doc/administration/merge_request_diffs.md:111:For source installations, these settings are nested under `external_diffs:` and
doc/administration/packages/container_registry.md:398:The default location where images are stored in source installations, is
doc/administration/packages/container_registry.md:1611:#### Source installations
doc/administration/packages/container_registry.md:1613:For source installations, locate your `registry` binary and temporarily replace it with the one
doc/administration/terraform_state.md:17:- `/home/git/gitlab/shared/terraform_state` for source installations.
doc/administration/terraform_state.md:105:- Nested under `terraform_state:` and then `object_store:` on source installations.
doc/administration/terraform_state.md:131:- For source installations:
doc/administration/redis/troubleshooting.md:105: # For source installations
doc/administration/object_storage.md:391:- For source installations, Workhorse also needs to be configured with Azure
doc/administration/object_storage.md:839:With Omnibus and source installations it is possible to split a single
doc/integration/kerberos.md:47:For source installations, make sure the `kerberos` gem group
doc/integration/kerberos.md:248:**For source installations with HTTPS**
doc/raketasks/cleanup.md:29:# installation from source
doc/raketasks/cleanup.md:63:# installation from source
doc/raketasks/cleanup.md:90:# installation from source
doc/raketasks/cleanup.md:126:# installation from source
doc/raketasks/cleanup.md:215:# installation from source
doc/raketasks/user_management.md:20:# installation from source
doc/raketasks/user_management.md:32:# installation from source
doc/raketasks/user_management.md:46:# installation from source
doc/raketasks/user_management.md:58:# installation from source
doc/raketasks/user_management.md:72:# installation from source
doc/raketasks/user_management.md:99:# installation from source
doc/raketasks/user_management.md:129: # installation from source
doc/raketasks/user_management.md:141: # installation from source
doc/raketasks/user_management.md:159: # installation from source
doc/raketasks/user_management.md:173:# installation from source
doc/raketasks/restore_gitlab.md:214:## Restore for installation from source
doc/raketasks/backup_gitlab.md:138:For installation from source:
doc/update/index.md:42:### Installation from source
doc/update/deprecations.md:490:The option to run self-managed installations of GitLab on a single database is now deprecated. From GitLab 17.0, we will require a [separate database for CI features](https://gitlab.com/groups/gitlab-org/-/epics/7509). With this change, self-managed versions of GitLab will behave similarly to GitLab.com. This change applies to installation methods with Omnibus GitLab, GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source. Before upgrading to GitLab 17.0, please ensure [migration](https://docs.gitlab.com/ee/administration/postgresql/multiple_databases.html) to two databases.
doc/install/install_methods.md:32:See the [installation from source guide](installation.md) and the [installation guides](https://about.gitlab.com/install/) for more information.
doc/development/documentation/styleguide/word_list.md:681:## Installation from source
doc/administration/pages/index.md:526:For installation from source, this can be fixed by installing the custom Certificate
doc/administration/file_hooks.md:38: For an installation from source the path is usually
doc/administration/postgresql/external.md:20:1. Set up a `gitlab` user with a password of your choice, create the `gitlabhq_production` database, and make the user an owner of the database. You can see an example of this setup in the [installation from source documentation](../../install/installation.md#7-database).
doc/administration/auth/jwt.md:52: For installation from source:
doc/administration/auth/oidc.md:111: For installation from source:
doc/administration/auth/oidc.md:671:For installation from source:
doc/administration/auth/oidc.md:811:For installation from source:
doc/administration/auth/oidc.md:890:For installation from source:
doc/administration/auth/oidc.md:967:For installation from source:
doc/administration/server_hooks.md:80: - For an installation from source, the path is usually `/home/git/repositories/<group>/<project>.git`.
doc/administration/geo/setup/external_database.md:214:1. Set up a `gitlab_geo` user with a password of your choice, create the `gitlabhq_geo_production` database, and make the user an owner of the database. You can see an example of this setup in the [installation from source documentation](../../../install/installation.md#7-database).
doc/administration/logs/index.md:649:- Installation from source: `/home/git/gitaly/gitlab-shell.log`
doc/administration/redis/troubleshooting.md:138:## Troubleshooting a non-bundled Redis with an installation from source
doc/integration/salesforce.md:70: For installation from source: