Historically, GitSwarm has been storing shared files in many different directories: public/uploads, builds, tmp/repositories, tmp/rebase (EE), etc. Having so many shared directories makes it difficult to deploy GitSwarm on shared storage (e.g. NFS). Working towards GitSwarm 2016.3 we are consolidating these different directories under the shared directory.
This means that if GitSwarm will start storing puppies in some future version then we should put them in shared/puppies. Temporary puppy files should be stored in shared/tmp.
In the GitSwarm application code you can get the full path to the shared directory with Gitlab.config.shared.path.
Files that belong to only one process, or on only one server, should not go in shared. Examples include PID files and sockets.
Sometimes you create a temporary file on disk with the intention of it becoming 'official'. For example you might be first streaming an upload from a user to disk in a temporary file so you can perform some checks on it. When the checks pass, you make the file official. In scenarios like this please follow these rules:
shared/tmp, i.e. on the same filesystem you want the official file to be on.