summaryrefslogtreecommitdiff
path: root/doc/development/shared_files.md
blob: e26464a5d805961eb2bd5718e6fa684e18aa4b30 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
---
stage: none
group: unassigned
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---

# Shared files

Historically, GitLab supported storing files that could be accessed from multiple application
servers in `shared/`, using a shared storage solution like NFS. Although this is still an option for
some GitLab installations, it must not be the only file storage option for a given feature. This is
because [cloud-native GitLab installations do not support it](architecture.md#adapting-existing-and-introducing-new-components).

Our [uploads documentation](uploads.md) describes how to handle file storage in
such a way that it supports both options: direct disk access and object storage.