mirror of
https://github.com/bitwarden/help
synced 2025-12-14 15:23:25 +00:00
21 lines
1.2 KiB
Markdown
21 lines
1.2 KiB
Markdown
---
|
|
layout: article
|
|
title: Self-hosting Send
|
|
categories: [send]
|
|
featured: true
|
|
popular: false
|
|
tags: []
|
|
order: "08"
|
|
description: "This article describes steps you may need to take to use Bitwarden Send in a self-hosted environment."
|
|
---
|
|
|
|
Once you [update your instance]({{site.baseurl}}/article/updating-on-premise/), most implementations will be already setup to begin [using Send]({{site.baseurl}}/article/create-send/). An exception to this is if you're using a non-default **mapped volume for attachment storage**.
|
|
|
|
The files attached to File Sends are stored in a `send` subdirectory of the existing attachments volume (i.e. `./bwdata/core/attachments/send`). This is dictated by the `globalSettings__send__baseDirectory=` environment variable, which has the following default configuration in `global.override.env`:
|
|
|
|
```
|
|
globalSettings__send__baseDirectory=/etc/bitwarden/core/attachments/send
|
|
```
|
|
|
|
If you want to store the files attached to File Sends in your non-default attachments volume, you'll need to point `globalSettings__send__baseDirectory=` to the new volume. For more information, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/).
|