Delivers highly-customized news feeds to Discord!
To use the publicly hosted instance for free, visit https://monitorss.xyz!
Docker is required to easily coordinate and run multiple services at once.
Note
General knowledge of how Docker, Docker volumes, and docker compose works is highly recommended to avoid accidental data loss
Note
Request history and delivery logs stored in PostgreSQL are not meant to be persistent forever. They may be removed when PostgreSQL versions are upgraded.
- Install Docker Engine
- Install Docker Compose
- Go to the Releases page and download the
docker-compose-<version>.ymlfile from the latest release - Download the
.env.examplefile into the same directory as the compose file and rename it to.env.prod - Create a Discord application through Discord's developer portal if you do not already have one
- Replace all relevant values in the
.env.prodfile with your own values- If you have your own MongoDB instance, set
BACKEND_API_MONGODB_URIto your MongoDB URI - Add your email at the end of
FEED_REQUESTS_FEED_REQUEST_DEFAULT_USER_AGENTfor feed hosts to be able to contact you if you violate their usage policies. For example,MonitoRSS [Self-Hosted]/1.0 [email protected]. - Replace all instances of "BOT_TOKEN_HERE" with your Discord bot application token
- Replace all instances of "BOT_CLIENT_ID_HERE" with your Discord bot application ID
- Replace all instances of "BOT_CLIENT_SECRET_HERE" with your Discord bot application secret
- Set
BACKEND_API_SESSION_SECRETto a random 64-character string - Set
BACKEND_API_SESSION_SALTto a random 16-character string - Add
http://localhost:8000/api/v1/discord/callback-v2to the list of redirect URIs in your Discord application in the OAuth2 page
- If you have your own MongoDB instance, set
- Run
docker compose -f docker-compose-<version>.yml up -d(replace<version>with the version you downloaded)- Make sure all containers, except those with "migration" in it, are running via
docker ps - Any containers ending in
-migrationdo not need to be running after initial setup - If any containers are failing to start, troubleshoot by getting the last few logs for the container with
docker logs <container_name or ID> --tail 100
- Make sure all containers, except those with "migration" in it, are running via
- Access the control panel via http://localhost:8000
- Set up your domain to point to the server running the control panel on localhost
- Update all references to
http://localhost:8000in your.env.prodto your desired domain. For example,https://mynewdomain.com. - Add
{DOMAIN_HERE}/api/v1/discord/callback-v2to the list of redirect URIs in your Discord application in the OAuth2 page, replacing{DOMAIN_HERE}with the value you set in step 1
While email notifications are available so that you may get notified when feeds are disabled for various reasons (permission erorrs, request errors, etc), credentials must be set to be able to send them out. Set the three variables below with your email provider's SMTP settings in your env file:
BACKEND_API_SMTP_HOSTBACKEND_API_SMTP_USERNAMEBACKEND_API_SMTP_PASSWORDBACKEND_API_SMTP_FROM
Make sure to opt into email notifications in the control panel's user settings page afterwards.
- Create a Reddit application at https://www.reddit.com/prefs/apps as a "web app".
- Add
{DOMAIN_HERE}/api/v1/reddit/callbackto the list of redirect URIs in your Reddit application settings, replacing{DOMAIN_HERE}with your domain that you're using to access the control panel. - Copy the redirect URI you just added and set it as
BACKEND_API_REDDIT_REDIRECT_URIin your.env.prodfile. - Copy the Reddit application's client ID (under "web app" label) and set it as
BACKEND_API_REDDIT_CLIENT_IDin your.env.prodfile. - Copy the Reddit application's secret and set it as
BACKEND_API_REDDIT_CLIENT_SECRETin your.env.prodfile. - Generate a random 64-digit hexadecimal string and set it as
BACKEND_API_ENCRYPTION_KEY_HEXin your.env.prodfile. One option is to use an online generator such as this one.
To update to a new release:
- Make a backup of your MongoDB data just in case since data migrations may occur
- Download the new
docker-compose-<version>.ymlfile from the Releases page - Stop containers with
docker compose -f docker-compose-<old-version>.yml down - Start containers with
docker compose -f docker-compose-<new-version>.yml up -d
If you've been using MonitoRSS v6 (used by the repo https://github.com/synzen/MonitoRSS-Clone), these are the instructions to migrate to v7.
It's recommended that you don't delete your v6 files until you've confirmed that all your feeds are working as expected post-migration.
- Follow the Self Host instructions above. The clone repo is no longer used or maintained.
- In your
.env.prodfile, setBACKEND_API_MONGODB_URIto your existing MongoDB URI - Run
docker compose -f docker-compose-<version>.yml up -d - Access the control panel via http://localhost:8000/servers and convert all your legacy feeds to personal feeds. Legacy feed articles will not be fetched/delivered until they are converted to personal feeds.
- After verifying that all is working as expected, you may delete your v6 files.