diff options
author | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-24 03:48:08 +0300 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-06-03 21:13:53 +0300 |
commit | 5a4bab0853fb56121bca943526e3b4186ed44d87 (patch) | |
tree | 515dfa4546543b9387b5951bd6b8847fc4634a09 /doc/install/google_cloud_platform | |
parent | 8a2afff06134447bcf80d39bcb1a5e378789df06 (diff) |
Clean up docs under install/
This is an initiative to ensure all documentation complies completely
with the Documentation Style Guide section "Documentation is the single
source of truth (SSOT)" according to this epic
https://gitlab.com/groups/gitlab-org/-/epics/1280.
In particular, the changes of this commit touch all files under
doc/install/. Most notably:
- install/redis.md:
Redirect to Redis section of install guide.
- install/pivotal/index.md:
Changed its content to reflect the current status, which is no
longer supported (since 2017!).
- install/google-protobuf.md:
Incorporated inside installation.md under the troubleshooting section.
- install/openshift_and_gitlab.md:
Clarified that this guide is no longer relevant. We might want to
redirect to the Chart docs in the future.
- install/structure.md:
Incorporated inside installation.md under its own section.
- install/kubernetes/index.md:
Redirected to https://docs.gitlab.com/charts
Diffstat (limited to 'doc/install/google_cloud_platform')
-rw-r--r-- | doc/install/google_cloud_platform/img/gcp_landing.png | bin | 9978 -> 0 bytes | |||
-rw-r--r-- | doc/install/google_cloud_platform/index.md | 24 |
2 files changed, 17 insertions, 7 deletions
diff --git a/doc/install/google_cloud_platform/img/gcp_landing.png b/doc/install/google_cloud_platform/img/gcp_landing.png Binary files differdeleted file mode 100644 index 92a9873728c..00000000000 --- a/doc/install/google_cloud_platform/img/gcp_landing.png +++ /dev/null diff --git a/doc/install/google_cloud_platform/index.md b/doc/install/google_cloud_platform/index.md index 242ad70ae82..77c61acbfd4 100644 --- a/doc/install/google_cloud_platform/index.md +++ b/doc/install/google_cloud_platform/index.md @@ -1,14 +1,13 @@ --- description: 'Learn how to install a GitLab instance on Google Cloud Platform.' +type: howto --- # Installing GitLab on Google Cloud Platform -![GCP landing page](img/gcp_landing.png) +This guide will help you install GitLab on a [Google Cloud Platform (GCP)][gcp] instance. -Getting started with GitLab on a [Google Cloud Platform (GCP)][gcp] instance is quick and easy. - -NOTE: **Note:** +NOTE: **Alternative installation method:** Google provides a whitepaper for [deploying production-ready GitLab on Google Kubernetes Engine](https://cloud.google.com/solutions/deploying-production-ready-gitlab-on-gke), including all steps and external resource configuration. These are an alternative to using a GCP VM, and use @@ -26,10 +25,9 @@ Once you have performed those two steps, you can [create a VM](#creating-the-vm) ## Creating the VM -To deploy GitLab on GCP you need to follow five simple steps: - -1. Go to <https://console.cloud.google.com/compute/instances> and login with your Google credentials. +To deploy GitLab on GCP you first need to create a virtual machine: +1. Go to <https://console.cloud.google.com/compute/instances> and log in with your Google credentials. 1. Click on **Create** ![Search for GitLab](img/launch_vm.png) @@ -142,3 +140,15 @@ Kerberos, etc. Here are some documents you might be interested in reading: [ssh]: https://cloud.google.com/compute/docs/instances/connecting-to-instance "Connecting to Linux Instances" [omni-smtp]: https://docs.gitlab.com/omnibus/settings/smtp.html#smtp-settings "Omnibus GitLab SMTP settings" [omni-ssl]: https://docs.gitlab.com/omnibus/settings/nginx.html#enable-https "Omnibus GitLab enable HTTPS" + +<!-- ## Troubleshooting + +Include any troubleshooting steps that you can foresee. If you know beforehand what issues +one might have when setting this up, or when something is changed, or on upgrading, it's +important to describe those, too. Think of things that may go wrong and include them here. +This is important to minimize requests for support, and to avoid doc comments with +questions that you know someone might ask. + +Each scenario can be a third-level heading, e.g. `### Getting error message X`. +If you have none to add when creating a doc, leave this section in place +but commented out to help encourage others to add to it in the future. --> |