mirror of
https://github.com/sct/overseerr.git
synced 2025-12-30 17:49:17 +01:00
docs: setup docusaurus for documentation (#848)
* docs: setup docusaurus for documentation * docs: setup tailwind content for docusaurus * chore: ensure tailwindcss is installed so pages deploy works * docs: add cname to point to docs * ci: override format checking for pnpm-lock in gen-docs folder * docs(gen-docs): readme for docusaurus * chore(gen-docs): remove unnecessary image files * docs: remove installation instructions (moved to docs) * ci: rename docusaurus workflows to a more explicit name * style(gen-docs): custom color for links * docs: add more doc pages * style: gradient menu link bg, proper jellyseerr font & footer bg color * docs: fix proper link to relative pages * style: tab-items also now uses the proper jellyseerr colors * style: use prismTheme shadesOfPurple for codeblock/syntax highlighting * docs: fix broken links * docs: fix broken links * docs: fix broken anchors * chore(gen-docs): local search bar * style(gen-docs): tab colors * docs: reverse-proxy documentation * style(gen-docs): jellyseerr-like cards * docs: rename baremetal to build from source * docs: nixpkg version check component * docs: conditionally render override package derivation block and admonitions * docs: users section of the documentation
This commit is contained in:
27
docs/using-jellyseerr/notifications/discord.md
Normal file
27
docs/using-jellyseerr/notifications/discord.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: Discord
|
||||
description: Configure Discord notifications.
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Discord
|
||||
|
||||
The Discord notification agent enables you to post notifications to a channel in a server you manage.
|
||||
|
||||
:::info
|
||||
Users can optionally opt-in to being mentioned in Discord notifications by configuring their [Discord user ID](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID-) in their user settings.
|
||||
:::
|
||||
|
||||
## Configuration
|
||||
|
||||
### Webhook URL
|
||||
|
||||
You can find the webhook URL in the Discord application, at **Server Settings → Integrations → Webhooks**.
|
||||
|
||||
### Bot Username (optional)
|
||||
|
||||
If you would like to override the name you configured for your bot in Discord, you may set this value to whatever you like!
|
||||
|
||||
### Bot Avatar URL (optional)
|
||||
|
||||
Similar to the bot username, you can override the avatar for your bot.
|
||||
50
docs/using-jellyseerr/notifications/email.md
Normal file
50
docs/using-jellyseerr/notifications/email.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Email
|
||||
description: Configure email notifications for your users.
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Email
|
||||
|
||||
## Configuration
|
||||
|
||||
:::info
|
||||
If the [Application URL](/using-jellyseerr/settings/general#application-title) setting is configured in **Settings → General**, Jellyseerr will explicitly set the origin server hostname when connecting to the SMTP host.
|
||||
:::
|
||||
|
||||
### Sender Name (optional)
|
||||
|
||||
Configure a friendly name for the email sender (e.g., "Jellyseerr").
|
||||
|
||||
### Sender Address
|
||||
|
||||
Set this to the email address you would like to appear in the "from" field of the email message.
|
||||
|
||||
Depending on your email provider, this may need to be an address you own. For example, Gmail requires this to be your actual email address.
|
||||
|
||||
### SMTP Host
|
||||
|
||||
Set this to the hostname or IP address of your SMTP server.
|
||||
|
||||
### SMTP Port
|
||||
|
||||
Set this to a supported port number for your SMTP host. `465` and `587` are commonly used.
|
||||
|
||||
### Encryption Method
|
||||
|
||||
In most cases, [Use Implicit TLS](https://tools.ietf.org/html/rfc8314) should be selected for port 465, and [Use STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) if available for port 587. Please refer to your email provider's documentations for details on how to configure this setting.
|
||||
|
||||
The default value for this setting is **Use STARTTLS if available**.
|
||||
|
||||
### SMTP Username & Password
|
||||
|
||||
:::info
|
||||
If your account has two-factor authentication enabled, you may need to create an application password instead of using your account password.
|
||||
:::
|
||||
Configure these values as appropriate to authenticate with your SMTP host.
|
||||
|
||||
### PGP Private Key & Password (optional)
|
||||
|
||||
Configure these values to enable encrypting and signing of email messages using [OpenPGP](https://www.openpgp.org/). Note that individual users must also have their **PGP public keys** configured in their user settings in order for PGP encryption to be used in messages addressed to them.
|
||||
|
||||
When configuring the PGP keys, be sure to keep the entire contents of the key intact. For example, private keys always begin with `-----BEGIN PGP PRIVATE KEY BLOCK-----` and end with `-----END PGP PRIVATE KEY BLOCK-----`.
|
||||
25
docs/using-jellyseerr/notifications/index.mdx
Normal file
25
docs/using-jellyseerr/notifications/index.mdx
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: Notifications
|
||||
description: Configure notifications for your users.
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Notifications
|
||||
|
||||
## Supported Notification Agents
|
||||
|
||||
Jellyseerr currently supports the following notification agents:
|
||||
|
||||
import DocCardList from '@theme/DocCardList';
|
||||
|
||||
<DocCardList />
|
||||
|
||||
## Setting Up Notifications
|
||||
|
||||
Simply configure your desired notification agents in **Settings -> Notifications** in the Jellyseerr web UI.
|
||||
|
||||
Users can customize their notification preferences in their own user notification settings.
|
||||
|
||||
## Requesting New Notification Agents
|
||||
|
||||
If we do not currently support your preferred notification agent, feel free to [submit a feature request on GitHub](https://github.com/Fallenbagel/jellyseerr/issues). However, please be sure to search first and confirm that there is not already an existing request for the agent!
|
||||
23
docs/using-jellyseerr/notifications/webpush.md
Normal file
23
docs/using-jellyseerr/notifications/webpush.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: Web Push
|
||||
description: Configure web push notifications for your users.
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Web Push
|
||||
|
||||
The web push notification agent enables you and your users to receive Jellyseerr notifications in a supported browser.
|
||||
|
||||
This notification agent does not require any configuration, but is not enabled in Jellyseerr by default.
|
||||
|
||||
:::warning
|
||||
Web push notifications require a secure connection to your Jellyseerr instance. Refer to the [Reverse Proxy](/extending-jellyseerr/reverse-proxy) documentation for more information.
|
||||
:::
|
||||
|
||||
To set up web push notifications, simply enable the agent in **Settings → Notifications → Web Push**. You and your users will then be prompted to allow notifications in your web browser.
|
||||
|
||||
Users can opt out of these notifications, or customize the notification types they would like to subscribe to, in their user settings.
|
||||
|
||||
:::info
|
||||
Web push notifications offer a native notification experience without the need to install an app.
|
||||
:::
|
||||
Reference in New Issue
Block a user