Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/guilhemn/eprint-to-email
https://github.com/guilhemn/eprint-to-email
Last synced: 7 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/guilhemn/eprint-to-email
- Owner: GuilhemN
- License: mit
- Created: 2024-05-30T20:31:40.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2024-09-16T09:51:13.000Z (4 months ago)
- Last Synced: 2024-11-17T11:15:29.258Z (2 months ago)
- Language: TypeScript
- Size: 851 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# RSS to Email
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.
[Introductory post on my blog](https://appjeniksaan.nl/linked/rss-to-email-on-github-actions)
## How does it work
- 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
## Getting started
1. [Fork](../../fork) this repository
2. Update [feeds.ts](src/feeds.ts) with your favorite RSS feed(s)
3. Update the [cron schedule](.github/workflows/send-email.yaml#L5) in the workflow file
4. Add the following [repository variables](../../settings/variables/actions) in settings:
- `SMTP_SERVER` for example: smtp.gmail.com
- `SMTP_PORT` for example: 587
5. Add the following [repository secrets](../../settings/secrets/actions) in settings:
- `MAIL_TO` the mail address to send the email to
- `SMTP_USERNAME`
- `SMTP_PASSWORD`
6. Done :muscle:
| :warning: | The above variables and secrets can also be changed directly in the [workflow](.github/workflows/send-email.yaml), but be aware that if your repo is public that this could expose your credentials. |
| :-------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
## Pro and cons
:fire: your data stays in your own Github account
:snowflake: fully customizable email
:date: receive the updates when and where you want
:poop: might have to do some tweaking
## Cron schedule
Use [crontab guru](https://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](https://github.com/orgs/community/discussions/13454) for cron schedules.
## Screenshot
Below is a screenshot of how the [Daring Fireball](https://daringfireball.net/) updates use custom styling and my own blog has a generic style.
## Local dev server
This project includes a local dev server to view and modify the email template based on your RSS feeds.
Start the dev server:
```bash
npm install
npm run dev
```
## How does it work
Rendering the email starts in the [`renderEmail`](src/renderEmail.tsx) function. It will retrieve and parse the feeds, and trigger rendering the email with the [`Email`](src/email/Email.tsx) component.
## Build on top of
- [react-email](https://github.com/resendlabs/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 :heart:
- [vite](https://vitejs.dev/)\
For rendering and the dev server. Had to do some hacking to get it working well with HMR and my cache implementation is :poop:. But Vite itself is :fire:
- [dawidd6/action-send-mail](https://github.com/dawidd6/action-send-mail)\
Github Action to send out emails, just bring your own SMTP provider