Commit 83d3f7e052a93a90366127211e0c700582018584
Committed by
Dmitriy Zaporozhets
Dmitriy Zaporozhets
1 parent
7e93aaa6
Exists in
master
and in
4 other branches
Better header and detail why you need two times the storage. Also moving memory …
…and storage to the bottom, OS is more important.
Showing
1 changed file
with
11 additions
and
13 deletions
Show diff stats
doc/install/requirements.md
| 1 | -# Memory | ||
| 2 | - | ||
| 3 | -We recommend you to run GitLab on a server with at least 1GB of RAM memory. You can use it with 512MB of memory but you need to setup unicorn to use only 1 worker and you need at least 200MB of swap. On a server with 1.5GB of memory you are able to support 1000+ users. | ||
| 4 | - | ||
| 5 | - | ||
| 6 | -# Hard disk capacity | ||
| 7 | - | ||
| 8 | -The necessary hard disk space largely depends on the size of the repos you want | ||
| 9 | -to store in GitLab. But as a *rule of thumb* you should have at least twice as much | ||
| 10 | -free space as your all repos combined take up. Apart from a local hard drive you can also mount a volume that supports the network file system (NFS) protocol. This volume might be located on a file server, a network attached storage (NAS) device, a storage area network (SAN) or on an Amazon Web Services (AWS) Elastic Block Store (EBS) volume. | ||
| 11 | - | ||
| 12 | - | ||
| 13 | # Operating Systems | 1 | # Operating Systems |
| 14 | 2 | ||
| 15 | ## Linux | 3 | ## Linux |
| @@ -41,7 +29,6 @@ GitLab does **not** run on Windows and we have no plans of supporting it in the | @@ -41,7 +29,6 @@ GitLab does **not** run on Windows and we have no plans of supporting it in the | ||
| 41 | near future. Please consider using a virtual machine to run GitLab. | 29 | near future. Please consider using a virtual machine to run GitLab. |
| 42 | 30 | ||
| 43 | 31 | ||
| 44 | - | ||
| 45 | # Rubies | 32 | # Rubies |
| 46 | 33 | ||
| 47 | GitLab requires Ruby (MRI) 1.9.3 and several Gems with native components. | 34 | GitLab requires Ruby (MRI) 1.9.3 and several Gems with native components. |
| @@ -50,6 +37,17 @@ While it is generally possible to use other Rubies (like | @@ -50,6 +37,17 @@ While it is generally possible to use other Rubies (like | ||
| 50 | some work on your part. | 37 | some work on your part. |
| 51 | 38 | ||
| 52 | 39 | ||
| 40 | +# Memory | ||
| 41 | + | ||
| 42 | +We recommend you to run GitLab on a server with at least 1GB of RAM memory. You can use it with 512MB of memory but you need to setup unicorn to use only 1 worker and you need at least 200MB of swap. On a server with 1.5GB of memory you are able to support 1000+ users. | ||
| 43 | + | ||
| 44 | + | ||
| 45 | +# Storage | ||
| 46 | + | ||
| 47 | +The necessary hard disk space largely depends on the size of the repos you want | ||
| 48 | +to store in GitLab. But as a *rule of thumb* you should have at least twice as much | ||
| 49 | +free space as your all repos combined take up. You need twice the storage because [GitLab satellites](https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/structure.md) contain an extra copy of each repo. Apart from a local hard drive you can also mount a volume that supports the network file system (NFS) protocol. This volume might be located on a file server, a network attached storage (NAS) device, a storage area network (SAN) or on an Amazon Web Services (AWS) Elastic Block Store (EBS) volume. | ||
| 50 | + | ||
| 53 | 51 | ||
| 54 | # Installation troubles and reporting success or failure | 52 | # Installation troubles and reporting success or failure |
| 55 | 53 |