# Preparation

There are some things we need to do in preparation to install this service.

## Volumes

<details id="bkmrk-media-folders-radarr"><summary>Persistent Data</summary>

This is where the service will store its own application data and ensures we can quickly update the service image.

<p class="callout warning">Ensure your user has permissions to access the folder.</p>

</details>## Environment

<details id="bkmrk-tz-this-is-the-curre"><summary>DB\_USER</summary>

This is the user name that will be used behind the scenes to log into the database.

<p class="callout info">*For example:* fider\_admin</p>

</details><details id="bkmrk-gid-%C2%A0"><summary>BASE\_URL</summary>

This is the URL that the service will be hosted and accessible through.

<p class="callout info">*For example:* fider.example.com</p>

</details><details id="bkmrk-email_noreply-this-i"><summary>EMAIL\_NOREPLY</summary>

This is the email address that will be attached to email notifications and should not be replied to because the inbox is not monitored or is non existent.

<p class="callout info">*For example:* noreply@fider.example.com</p>

</details><details id="bkmrk-email_smtp_host-this"><summary>EMAIL\_SMTP\_HOST</summary>

This is the host address of your email server.

<p class="callout info">*For example:* smtp.gmail.com</p>

</details><details id="bkmrk-email_smtp_port-this"><summary>EMAIL\_SMTP\_PORT</summary>

This is the port used by your email server.

<p class="callout info">*For example:* 587</p>

</details><details id="bkmrk-email_smtp_username-"><summary>EMAIL\_SMTP\_USERNAME</summary>

This is the account user name used by your email server.

<p class="callout info">*For example:* example@gmail.com</p>

</details><details id="bkmrk-email_smtp_enable_st"><summary>EMAIL\_SMTP\_ENABLE\_STARTTLS</summary>

This enables [StartTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS), which is used by the email server to upgrade insecure connections to one using TLS or SSL.

<p class="callout info">*Recommended:* true</p>

</details>### Passwords

<p class="callout danger">Keep these securely stored in a password manager, such as [VaultWarden](https://hub.subspace.services/books/vaultwarden "VaultWarden").</p>

<details id="bkmrk-db_root_pass-this-is"><summary>DB\_PASS</summary>

This is the password that will be used for root access to the database.

<p class="callout warning">It is important to use secure, randomly generated password.</p>

You can use a random alphanumeric string from a password manager, or open the terminal and run the command:

```
tr -dc 'A-Za-z0-9!"#$%&'\''()*+,-./:;<=>?@[\]^_`{|}~' </dev/urandom | head -c 32; echo
```

This pulls a random string from the '[urandom](https://en.wikipedia.org/wiki//dev/random)' device, removes unwanted characters and trim it to an appropriate length.

</details><details id="bkmrk-jwt_secret-this-is-t"><summary>JWT\_SECRET</summary>

This is the secret that will be used for validating users who are logged into the service.

<p class="callout warning">It is important to use secure, randomly generated token.</p>

You can use a random alphanumeric string from a password manager, or open the terminal and run the command:

```
tr -dc 'A-Za-z0-9!' </dev/urandom | head -c 32; echo
```

This pulls a random string from the '[urandom](https://en.wikipedia.org/wiki//dev/random)' device, removes unwanted characters and trim it to an appropriate length.

</details><details id="bkmrk-owncloud_admin_passw"><summary>EMAIL\_SMTP\_PASSWORD</summary>

This is the password for logging into your email account for sending administrative notifications.

<p class="callout warning">When possible, you should use app passwords.</p>

</details>