v1.4.0

In preparation of breaking changes in Plex Media Server version 1.32.7.7484, Autoscan 1.4.0 updates the HTTP method used to refresh paths. More details are available in #218 and #219.

In addition, @voltron4lyfe and @rg9400's Readarr contribution finally made it to a release!

Full Changelog: v1.3.0...v1.4.0

v1.3.0

Today is the day that Bernard is finally getting deprecated! Gone are the days of having to periodically delete Bernard's database because it messed up again. But... how do I enable Google Drive monitoring now? I'm glad you asked!

Introducing: A-Train

A-Train is the official successor of Bernard with a flawless history so far. However, A-Train isn't integrated into Autoscan directly.

While Autoscan officially supports A-Train, it must be run alongside Autoscan in a separate process or Docker container. For more information, please check out A-Train's readme! :)

Also please note that today we're releasing Autoscan 1.3. In compliance with semver, we haven't disabled or removed any Bernard code. However, we've removed all Bernard-related documentation as we highly encourage you to switch to A-Train.

What's Changed

• refactor: default config directory by @l3uddz in #109
• log: display current version by @l3uddz in #110
• feat: health check by @m-rots in #116
• feat(triggers): a-train by @m-rots in #115

Full Changelog: v1.2.0...v1.3.0

v1.2.0

A feature-packed Autoscan 1.2 release with huge credit to @l3uddz!

Note: the new database connector might fail to migrate your database the first time. Simply performing a restart of Autoscan should fix this issue. To be extra safe, make sure to update Autoscan when its queue is empty.

New features

• Autoscan now supports the new Radarr events. 6657d3c
• We now have an amazing web interface for you to submit your totally unnecessary manual scans!
• Jellyfin support!!! (Really depends on the version, no guarantees!)
• The ability to create infinite scan loops with the Autoscan target.
• Autoscan now provides some statistics in the logs.
• We have intentionally broken Bernard to get rid of data anomalies.
• We’re using a new experimental connector for the sqlite database.
• A database migrator! We’re sure you won’t miss the releases that required you to delete autoscan.db.

Bug fixes

• The 502 HTTP status is now handled correctly for all targets. 35464a7
• The processor won’t longer be started when no targets have been configured. Yes, it essentially was a /dev/null before…
• We’ve snapped incorrect library matching out of existence. 8e28242

v1.1.0

Fear no more! The malfunctioning host Bernard is slowly becoming less important to the Autoscan project.

With the addition of the EpisodeFileDelete, Rename and SeriesDelete events to Sonarr, Autoscan is now able to handle 99% of file system interactions originating from Sonarr!

Please do note that for files added outside of Sonarr, you will still need the Bernard or Inotify triggers to pick up all file system interactions.

New features

• Support for the EpisodeFileDelete, Rename and SeriesDelete Sonarr events.

Bug fixes

• Another attempt at preventing database lock errors.
• Inotify error handling was missing in the walk function.

v1.0.0

With 2020 coming to a close, @l3uddz and I worked on the last couple of tweaks to prepare Autoscan for 1.0.

Autoscan's 1.0 release guarantees that the config file and API will not see any major changes until a 2.0 release. In other words, no need to delete databases or change config files on 1.x version upgrades! In addition, the SQLite database will not be changed until a 2.0 release.

However, we can still add features to the config file and API as long as these are non-breaking.

OMG! A 1.0 release! Does this mean that Autoscan can be considered feature-complete?

Not yet! While the majority of features are in-place, there are still a couple of things (such as Jellyfin support) which are on our 1.x roadmap.

Okay... is it at-least bug-free then?

The core of Autoscan is considered bug-free. No bugs have survived the early access testing period.
However, two of Autoscan's dependencies, Bernard and FSNotify, are still hit-or-miss.

As the author of Bernard, I have not been able to track down the issues popping up for some users. Initially, Bernard was planned to become the building-block for many of my projects. However, the uncertain future of Google Drive has cancelled any future Bernard development.

Changelog

So, what changed?

New features

• Added a manual webhook/trigger for use by third party applications and scripts. d7d172b

Minor changes

• The time format in the logs now includes the date as well as the time in seconds. db7ee12

v0.4.2

A couple of minor changes which should make Autoscan more stable.

Minor changes

• Introduced a timeout between successful scans to reduce load on Plex.
• Autoscan no longer throws a fatal error when a path cannot be matched to a library. Instead, a warning will be printed to the logs.

v0.4.1

Some critical bug fixes for Bernard, Sonarr and Autoscan's datastore.

Bug fixes

• The database lock error should be gone for good now!
• The latest version of Sonarr changed the eventType to lowercase, so Autoscan switched to case insensitive matching.
• Squashed some Bernard inconsistencies.

v0.4.0

Introducing local file system monitoring and some final touches! 🥳

Breaking changes

• Removed multiple columns from Autoscan's datastore. To upgrade to 0.4.0, make sure you delete the autoscan.db file.
• Rewrite rules are now consistent (Bernard paths now start with a slash /), make sure to update your config accordingly.
• Removed retries from Autoscan's config file, make sure you remove this value from your config if it is currently set.
• Removed file existence checking. Please update the minimum-age value to add a safe buffer between scan ingress and egress.

New features

• Autoscan can now monitor your local file system for changes with the Inotify trigger!

v0.3.1

Minor bug fixes for the Bernard trigger.

v0.3.0

Introducing Google Drive monitoring! Woohoo! 🥳

Breaking changes

• Added removed column to Autoscan's datastore. To upgrade to 0.3.0, make sure you delete the autoscan.db file.
• The rewrite field in the config now accepts multiple rewriting rules. To upgrade to 0.3.0, make sure you write these rewrite rules in a list instead of a single item.

# 0.2.1
rewrite:
  from: /Media/*
  to: /mnt/unionfs/Media/$1

# 0.3.0
rewrite:
  - from: /Media/*
    to: /mnt/unionfs/Media/$1

New features

• Autoscan can now monitor your Google Drive for changes!
  Note: only Shared Drives are supported with authentication being done through Service Accounts.