This plugin automacially scans a users library (default every 4 hours), populates a list of recently added (not previously scanned) media, converts that data into HTML format, and sends out emails to a provided list of recipients.
- Imgur's API is one available option to upload poster images for newsletter emails to fetch images. Imgur (according to their Documentation) limits uploads to 12,500/day.
- HOWEVER, according to some documentation I have just discovered, there is a limit of 500 requests/hour for each user (IP address) hitting the API
- This plugin is configured to reference existing Images from previous scans (including current) as to not duplicate requests to Imgur and use up the daily upload limit
- Sign up to get an API key in order to use this plugin.
- Users can bypass this limitation as of V0.5.0 with the ability to use Jellyfin's API to serve images!
To ensure proper images are being pulled from Jellyfin's database, ensure you follow the standard Organization Scheme for naming and organizing your files. https://jellyfin.org/docs/general/server/media/books
If this format isn't followed properly, Jellyfin may have issue correctly saving the item's data in the proper database (the database that this plugin uses).
Shows
├── Series (2010)
│ ├── Season 00
│ │ ├── Some Special.mkv
│ │ ├── Episode S00E01.mkv
│ │ └── Episode S00E02.mkv
│ ├── Season 01
│ │ ├── Episode S01E01-E02.mkv
│ │ ├── Episode S01E03.mkv
│ │ └── Episode S01E04.mkv
│ └── Season 02
│ ├── Episode S02E01.mkv
│ ├── Episode S02E02.mkv
│ ├── Episode S02E03 Part 1.mkv
│ └── Episode S02E03 Part 2.mkv
└── Series (2018)
├── Episode S01E01.mkv
├── Episode S01E02.mkv
├── Episode S02E01-E02.mkv
└── Episode S02E03.mkv
Movies
├── Film (1990).mp4
├── Film (1994).mp4
├── Film (2008)
│ └── Film.mkv
└── Film (2010)
├── Film-cd1.avi
└── Film-cd2.avi
Testing and Frequency can be managed through your Dashboard > Scheduled Tasks
- There are 2 scheduled tasks:
- Email Newsletter: Which generates and sends out the newsletters via email from the data scanned from the task below
- Filesystem Scraper: Which scans your library, parses the data, and gets it ready for the email
Manifest is up an running! You can now import the manifest in Jellyfin and this plugin will appear in the Catalog!
- Go to "Plugins" on your "Dashboard"
- Go to the "Repositories" tab
- Click the '+' to add a new Repository
- Give it a name (i.e. Newsletters)
- In "Repository URL," put "https://raw.githubusercontent.com/Cloud9Developer/Jellyfin-Newsletter-Plugin/master/manifest.json"
- Click "Save"
- You should now see Jellyfin Newsletters in Catalog under the Category "Newsletters"
- Once installed, restart Jellyfin to activate the plugin and configure your settings for the plugin
- Recipients of the newsletter. Add add as many emails as you'd like, separated by commas.
- All emails will be sent out via BCC
- The address recipients will see on emails as the sender
- Defaults to [email protected]
- The subject of the email
- Select the item types you want to scan
- NOTE: this is Item types, not libraries
Allows for use of custom HTML formatting for emails! Defaults to original formatting, but can be modified now!
For defaults, see Jellyfin.Plugin.Newsletters/Templates/
- The main body of your email
- The formatting for each individual entry/series/movie that was found and will be sent out
- The type of poster hosting you want to use
- Options include:
- Imgur (Default)
- Local Hosting from Jellyfin's API
- Options include:
- Your Imgur API key (Client ID) to upload images to be available in the newsletter
- Your servername/hostname/DNS entry (and Port if applicable) to allow users to access images hosted locally on your server.
- i.e. https://myDNSentry.com:8096
- NOTE: do not put a trailing '/' at the end of the url
- i.e. https://myDNSentry.com:8096
- This is now used as a possible data tag! (even if you don't use self-hosting, set this if you want the
{ServerURL}to work)
- The email server address you want to use.
- Defaults to smtp.gmail.com
- The port number used by the email server above
- Defaults to gmail's port (587)
- Your username/email to authenticate to the SMTP server above
- Your password to authenticate to the SMTP server above
- I'm not sure about other email servers, but google requires a Dev password to be created.
- For gmail specific instructions, you can visit https://support.google.com/mail/answer/185833?hl=en for details
- I'm not sure about other email servers, but google requires a Dev password to be created.
Please leave a ticket in the Issues on this GitHub page and I will get to it as soon as I can. Please be patient with me, since I did this on the side of my normal job. But I will try to fix any issues that come up to the best of my ability and as fast as I can!
Some of these may not interest that average user (if anyone), but I figured I would have any element in the Newsletters.db be available for use!
NOTE: Examples of most tags can be found in the default Templates (template_modern_body.html AND template_modern_entry.html)
- {EntryData} - Needs to be inside of the 'Body' html
- {Date} - Auto-generated date of Newsletter email generation
- {SeasonEpsInfo} - This tag is the Plugin-generated Season/Episode data
- {Title} - Title of Movie/Series
- {SeriesOverview} - Movie/Series overview
- {ImageURL} - Poster image for the Movie/Series
- {Type} - Item type (Movie or Series)
- {PremiereYear} - Year Movie/Series was Premiered
- {RunTime} - Movie/Episode Duration (for Series, gives first found duration. Will fix for only single episode or average in future update)
- {OfficialRating} - TV-PG, TV-13, TV-14, etc.
- {CommunityRating} - Numerical rating stored in Jellyfin's metadata
These tags are available but not recommended to use. Untested behavior using these.
- {Filename} - File path of the Movie/Episode (NOT RECOMMENDED TO USE)
- {Season} - Season number of Episode (NOT RECOMMENDED TO USE)
- {Episode} - Episode number (NOT RECOMMENDED TO USE)
- {ItemID} - Jellyfin's assigned ItemID (NOT RECOMMENDED TO USE)
- {PosterPath} - Jellyfin's assigned Poster Path (NOT RECOMMENDED TO USE)
See 'issues' tab in GitHub with the lable 'bug'
If you would like to collaborate/contribute, feel free! Make all PR's to the 'development' branch and please note clearly what was added/fixed, thanks!