Stay on top of your favorite RSS feeds - on your own terms. This project allows you to set up custom email updates based on the RSS feeds you specify, all within the comfort of your own Github account.
Say goodbye to constantly checking for updates, and hello to staying informed on your own schedule.
- Github workflow runs on a schedule
- Workflow retrieves updates from your RSS feeds since its last successful run
- Workflow sends the updates through a SMTP server of your choice
- Fork this repository
- Update feeds.ts with your favorite RSS feed(s)
- Update the cron schedule in the workflow file
- Add the following repository variables in settings:
SMTP_SERVER
for example: smtp.gmail.comSMTP_PORT
for example: 587
- Add the following repository secrets in settings:
MAIL_TO
the mail address to send the email toSMTP_USERNAME
SMTP_PASSWORD
- Done ๐ช
The above variables and secrets can also be changed directly in the workflow, but be aware that if your repo is public that this could expose your credentials. |
---|
๐ฅ your data stays in your own Github account
โ๏ธ fully customizable email
๐ receive the updates when and where you want
๐ฉ might have to do some tweaking
Use crontab guru to play around with the cron schedule that works best for you.
Some example schedules:
cron | description |
---|---|
0 6 * * * | every day at 06:00 |
0 9-18 * * 1-5 | monday to friday every hour from 09:00 to 18:00 |
0 10 * * 6 | saturday at 10:00 |
0/15 * * * * | every 15 minutes |
Because the workflow looks at the previous successful run to determine which posts to send you, you can also disable the workflow by hand and pickup again later. There might be a limit to the amount of posts in a single RSS feed.
Note: Github workflow runs do not support timezones for cron schedules.
Below is a screenshot of how the Daring Fireball updates use custom styling and my own blog has a generic style.
This project includes a local dev server to view and modify the email template based on your RSS feeds.
Start the dev server:
npm install
npm run dev
Rendering the email starts in the renderEmail
function. It will retrieve and parse the feeds, and trigger rendering the email with the Email
component.
- react-email
This project is what triggered me to create this repo. It is still very beta, but if we can ditch all the clunky specialized tools for creating email layouts and replace them with a React / Typescript based solution โค๏ธ - vite
For rendering and the dev server. Had to do some hacking to get it working well with HMR and my cache implementation is ๐ฉ. But Vite itself is ๐ฅ - dawidd6/action-send-mail
Github Action to send out emails, just bring your own SMTP provider