# Prevent database migrations from running on upgrade automatically
gitlab_rails['auto_migrate']=false
```
...
...
@@ -385,13 +385,6 @@ are supported and can be added if needed.
## Configure Gitaly
NOTE:
[Gitaly Cluster](../gitaly/praefect.md) support
for the Reference Architectures is being
worked on as a [collaborative effort](https://gitlab.com/gitlab-org/quality/reference-architectures/-/issues/1) between the Quality Engineering and Gitaly teams. When this component has been verified
some Architecture specs will likely change as a result to support the new
and improved designed.
[Gitaly](../gitaly/index.md) server node requirements are dependent on data,
specifically the number of projects and those projects' sizes. It's recommended
that a Gitaly server node stores no more than 5TB of data. Although this
...
...
@@ -466,8 +459,7 @@ To configure the Gitaly server, on the server node you want to use for Gitaly:
alertmanager['enable']=false
prometheus['enable']=false
# Prevent database connections during 'gitlab-ctl reconfigure'
gitlab_rails['rake_cache_clear']=false
# Prevent database migrations from running on upgrade automatically
gitlab_rails['auto_migrate']=false
# Configure the gitlab-shell API callback URL. Without this, `git push` will
...
...
@@ -779,7 +771,6 @@ running [Prometheus](../monitoring/prometheus/index.md) and
grafana['admin_password']='toomanysecrets'
# Disable all other services
gitlab_rails['auto_migrate']=false
alertmanager['enable']=false
gitaly['enable']=false
gitlab_exporter['enable']=false
...
...
@@ -794,6 +785,9 @@ running [Prometheus](../monitoring/prometheus/index.md) and
unicorn['enable']=false
node_exporter['enable']=false
gitlab_exporter['enable']=false
# Prevent database migrations from running on upgrade automatically
gitlab_rails['auto_migrate']=false
```
1. Prometheus also needs some scrape configurations to pull all the data from the various