Skip to content

Releases: boranblok/nntpPoster

Version 0.4.1

07 Oct 07:25
Compare
Choose a tag to compare
Version 0.4.1 Pre-release
Pre-release

Minor service release.

This includes a DuplicateMessageThrottleFilter to limit log spam to a certain extent. This can be disabled if required by modifying the log4netconfig.xml file.

Additionally when a file gives errors during metadata stripping (ffmpeg or mkvtoolnix) it will be posted as is. Let me know if you would prefer this to be a folder level parameter instead.

Version 0.4

06 Oct 14:24
Compare
Choose a tag to compare
Version 0.4 Pre-release
Pre-release

This version mainly fixes a critical bug with reposting. A repost didn't have the watch folder config assigned and this would hang the uploader completely.

Included with this release is also the database update system which will create or update any database version to the latest version.

The database has also been modified to have system critical fields marked as not nullable to at least keep invalid data from causing an upload hang.

Version 0.3

04 Oct 18:06
Compare
Choose a tag to compare
Version 0.3 Pre-release
Pre-release

Major rewrite of the configuration subsystem. This allows for easier changes to the config to be saved to disk. As well as a better layout for things like lists and collections of multiple settings.

With this change multiple watch folders can be defined, each with a subset of custom settings (obfuscated or not, clean the name or not, what groups to post to, etc)

Added a command to the init.d.sh script cleanshutdown this executes a windows service pause (which is also supported now) this will stop the listening process, but continue the current upload, while this upload is running verification and notification will also continue. Once the current upload has finished the service shuts down. Depending on the current upload this can take quite a while.

Upgrading

Upgrading from an older version requires a complete removal of the database. This is normally the nntpAutoPoster.Sqlite3.db file in the application folder.

This also means it is recommended to have all current files posted, notified and verified.

This release also includes a version number in the sqlite databse, which will make this step no longer required on future updates, but for this version this is sadly a required step.

After this the new config file settings.config has to be filled in with the configuration. This file contains all the settings from the previous release, just in a different format.

Version 0.2

24 Aug 12:34
Compare
Choose a tag to compare
Version 0.2 Pre-release
Pre-release
  • Made the configuration much more logically organised
  • the default config do not require the user to modify any folders if he decides to use the included folders
  • Small bugfixes if the indexer does return 200 OK requests but gives error messages as response
  • Added a windows service executable, this is the new main executable
  • Added installation scripts for the windows service executable
  • Added an init.d sample script to set up autostart on linux systems.

edited the init.d.sh script to have correct encoding and line endings for a linux system

Version 0.1

03 Jul 18:35
Compare
Choose a tag to compare
Version 0.1 Pre-release
Pre-release

Version 0.1, first beta.