aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDiederick de Vries <diederick@diederickdevries.net>2018-06-14 20:44:03 +0200
committerDiederick de Vries <diederick@diederickdevries.net>2018-06-14 20:48:10 +0200
commit7f688ac5466ff1d38b487a436bd629e572093ef2 (patch)
tree2db71066b04221fff4c2718c2b75c58b0f451a22
parent648b4e51d9380dbc4f3866d6fc1183dcc22d8036 (diff)
downloadaftercare-7f688ac5466ff1d38b487a436bd629e572093ef2.tar.gz
aftercare-7f688ac5466ff1d38b487a436bd629e572093ef2.tar.bz2
aftercare-7f688ac5466ff1d38b487a436bd629e572093ef2.zip
Correct typos
-rw-r--r--README.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/README.md b/README.md
index 4c62e5b..e5b8d1a 100644
--- a/README.md
+++ b/README.md
@@ -1,20 +1,20 @@
1# Aftercare 1# Aftercare
2 2
3Aftercare is a somewhat naive media file post processing script in Groovy. Will move all series episodes under the input folder into neat per serie and per season directories under the output folder. It recognises episode files by their filename extension. The episodes will be renamed into the form 3Aftercare is a somewhat naive media file post processing script in Groovy. It will move all series episodes under the input folder into neat per serie and per season directories under the output folder. It recognises episode files by their filename extension. The episodes will be renamed into the form
4 4
5 Series Name - SxxExx.ext 5 Series Name - SxxExx.ext
6 6
7The media can be inside directories, but don't have to be. Afterwards these original directories and files will be moved to a done folder with their contents for you to inspect. When something fails, the failed original will me moved to the error folder. 7The media can be inside directories, but don't have to be. Afterwards these original directories and files will be moved to a `done` folder with their contents for you to inspect. When something fails, the failed original will me moved to the `error` folder.
8 8
9Naive in the sense that it expects original file names like these: 9Naive in the sense that it expects original file names like these:
10 10
11 The.Expanse.S03E07.720p.WEB.H264-DEFLATE.mkv 11 The.Expanse.S03E07.720p.WEB.H264-DEFLATE.mkv
12 12
13where the series title is everything before the season/episode numbers. The S and E can be lowecase as well, the s can be left out and the E can also be an uppercase or lowercase X. Any dots are replaced with spaces. Any apostrophes in the title are discarded. 13where the series title is everything before the season/episode numbers. The S and E can be lowercase as well, the S can be left out and the E can also be an uppercase or lowercase X. Any dots are replaced with spaces. Any apostrophes in the title are discarded.
14 14
15Rename and change the file named `example.conf` and configure which directories, user, group and unix rights should be used: 15Rename and change the file named `example.conf` and configure which directories, user, group and unix rights should be used:
16 16
17 output The directory under which your media renderer expects the media files. 17 output The directory under which your media renderer expects the media files
18 input The directory where the originals are 18 input The directory where the originals are
19 done The directory where the succesful originals are moved 19 done The directory where the succesful originals are moved
20 error The directory where the failed originals are moved 20 error The directory where the failed originals are moved
@@ -28,11 +28,11 @@ Rename and change the file named `example.conf` and configure which directories,
28 allowed a list of allowed file types 28 allowed a list of allowed file types
29 nrs a regex matching with how the original filenames state their series and episode number. 29 nrs a regex matching with how the original filenames state their series and episode number.
30 30
31You can run the script manually (`sudo` to set the unix user, group and rights): 31You can run the script manually (use of `sudo` is to set the unix user, group and rights):
32 32
33 $ sudo groovy aftercare.groovy properties.conf 33 $ sudo groovy aftercare.groovy properties.conf
34 34
35but you shouldn't. The two `systemd` files will let you run the script automatically every hour. In `aftercare.service`, adapt the line starting with `ExecStart` to point it to where you install Aftercare. Put both files in `/etc/systemd/system/` and do: 35but you shouldn't. The two `systemd` files will let you run the script automatically every hour and will make the script's log messages appear in the system logs. In `aftercare.service`, adapt the line starting with `ExecStart` to point it to where you install Aftercare. Put both files in `/etc/systemd/system/` and do:
36 36
37 $ sudo systemctl start aftercare.timer 37 $ sudo systemctl start aftercare.timer
38 $ sudo systemctl enable aftercare.timer 38 $ sudo systemctl enable aftercare.timer