dropcaster 0.0.4 → 0.0.5.rc1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: f4e905930e1f1dc2001966418faab10c4c7a4ac3
4
+ data.tar.gz: d9167156b2e41e7b3e3c340dedb8cbdcc0ba845a
5
+ SHA512:
6
+ metadata.gz: 687de91b7d1b129b62adbe848fa307717d0f1aa02a7151397dd1885af86f1733d9e3d8c01f38986f2918616e8c92244d83701f166b68a42c41db8eeaad41673c
7
+ data.tar.gz: b2d4220b02472c4a23dcc3b803cb1ffab514731333116cb236840868ff7cf7133907de84f0e04e8c135d7f923f214f9eb2010ee6f51515938fec59df4e2cdf05
data/.document CHANGED
@@ -1,5 +1,5 @@
1
- lib/**/*.rb
2
- bin/*
3
- -
4
- features/**/*.feature
5
- LICENSE.txt
1
+ lib/**/*.rb
2
+ bin/*
3
+ -
4
+ features/**/*.feature
5
+ LICENSE.txt
data/.gitignore ADDED
@@ -0,0 +1,14 @@
1
+ # rcov generated
2
+ coverage
3
+
4
+ # rdoc generated
5
+ rdoc/
6
+
7
+ # yard generated
8
+ .yardoc
9
+
10
+ # bundler
11
+ .bundle
12
+
13
+ # jeweler generated
14
+ pkg
data/.travis.yml ADDED
@@ -0,0 +1,6 @@
1
+ language: ruby
2
+ bundler_args: --without development
3
+ rvm:
4
+ - 1.9.3
5
+ - 2.0.0
6
+ - 2.1.0
data/Gemfile CHANGED
@@ -1,13 +1,2 @@
1
- source :rubygems
2
-
3
- gem 'ruby-mp3info'
4
- gem 'activesupport'
5
-
6
- group :development do
7
- gem "rake", "0.8.7" # http://stackoverflow.com/questions/6085610
8
- gem "bundler", "~> 1.0.0"
9
- gem "jeweler", "~> 1.6.4"
10
- gem 'libxml-ruby'
11
- gem 'rdoc'
12
- gem 'json'
13
- end
1
+ source 'https://rubygems.org'
2
+ gemspec
data/Gemfile.lock CHANGED
@@ -1,29 +1,94 @@
1
- GEM
2
- remote: http://rubygems.org/
3
- specs:
4
- activesupport (3.0.10)
5
- git (1.2.5)
6
- jeweler (1.6.4)
7
- bundler (~> 1.0)
8
- git (>= 1.2.5)
9
- rake
10
- json (1.5.3)
11
- libxml-ruby (2.2.1)
12
- libxml-ruby (2.2.1-x86-mingw32)
13
- rake (0.8.7)
14
- rdoc (3.9.3)
15
- ruby-mp3info (0.6.15)
16
-
17
- PLATFORMS
18
- ruby
19
- x86-mingw32
20
-
21
- DEPENDENCIES
22
- activesupport
23
- bundler (~> 1.0.0)
24
- jeweler (~> 1.6.4)
25
- json
26
- libxml-ruby
27
- rake (= 0.8.7)
28
- rdoc
29
- ruby-mp3info
1
+ PATH
2
+ remote: .
3
+ specs:
4
+ dropcaster (0.0.5.rc1)
5
+ activesupport (~> 3.2)
6
+ ruby-mp3info (~> 0.8)
7
+
8
+ GEM
9
+ remote: https://rubygems.org/
10
+ specs:
11
+ activesupport (3.2.17)
12
+ i18n (~> 0.6, >= 0.6.4)
13
+ multi_json (~> 1.0)
14
+ binding_of_caller (0.7.2)
15
+ debug_inspector (>= 0.0.1)
16
+ celluloid (0.15.2)
17
+ timers (~> 1.1.0)
18
+ celluloid-io (0.15.0)
19
+ celluloid (>= 0.15.0)
20
+ nio4r (>= 0.5.0)
21
+ coderay (1.1.0)
22
+ debug_inspector (0.0.2)
23
+ ffi (1.9.3)
24
+ formatador (0.2.4)
25
+ guard (2.4.0)
26
+ formatador (>= 0.2.4)
27
+ listen (~> 2.1)
28
+ lumberjack (~> 1.0)
29
+ pry (>= 0.9.12)
30
+ thor (>= 0.18.1)
31
+ guard-bundler (2.0.0)
32
+ bundler (~> 1.0)
33
+ guard (~> 2.2)
34
+ guard-minitest (2.2.0)
35
+ guard (~> 2.0)
36
+ minitest (>= 3.0)
37
+ i18n (0.6.9)
38
+ libnotify (0.8.2)
39
+ ffi (>= 1.0.11)
40
+ libxml-ruby (2.7.0)
41
+ libxml-ruby (2.7.0-x86-mingw32)
42
+ listen (2.5.0)
43
+ celluloid (>= 0.15.2)
44
+ celluloid-io (>= 0.15.0)
45
+ rb-fsevent (>= 0.9.3)
46
+ rb-inotify (>= 0.9)
47
+ lumberjack (1.0.4)
48
+ method_source (0.8.2)
49
+ minitest (5.2.3)
50
+ multi_json (1.8.4)
51
+ nio4r (1.0.0)
52
+ pry (0.9.12.4)
53
+ coderay (~> 1.0)
54
+ method_source (~> 0.8)
55
+ slop (~> 3.4)
56
+ pry (0.9.12.4-x86-mingw32)
57
+ coderay (~> 1.0)
58
+ method_source (~> 0.8)
59
+ slop (~> 3.4)
60
+ win32console (~> 1.3)
61
+ pry-nav (0.2.3)
62
+ pry (~> 0.9.10)
63
+ pry-stack_explorer (0.4.9.1)
64
+ binding_of_caller (>= 0.7)
65
+ pry (>= 0.9.11)
66
+ rake (10.1.1)
67
+ rb-fsevent (0.9.4)
68
+ rb-inotify (0.9.3)
69
+ ffi (>= 0.5.0)
70
+ rb-readline (0.5.1)
71
+ ruby-mp3info (0.8.2)
72
+ slop (3.4.7)
73
+ thor (0.18.1)
74
+ timers (1.1.0)
75
+ win32console (1.3.2-x86-mingw32)
76
+
77
+ PLATFORMS
78
+ ruby
79
+ x86-mingw32
80
+
81
+ DEPENDENCIES
82
+ bundler (~> 1.5)
83
+ dropcaster!
84
+ guard-bundler (~> 2.0)
85
+ guard-minitest (~> 2.2)
86
+ libnotify (~> 0.8)
87
+ libxml-ruby (~> 2.7)
88
+ pry (~> 0.9)
89
+ pry-nav (~> 0.2)
90
+ pry-stack_explorer (~> 0.4)
91
+ rake (~> 10.1)
92
+ rb-fsevent (~> 0.9)
93
+ rb-inotify (~> 0.9)
94
+ rb-readline (~> 0.5)
data/Guardfile ADDED
@@ -0,0 +1,12 @@
1
+ guard 'bundler' do
2
+ watch('Gemfile')
3
+ watch(%r|^.*\.gemspec|)
4
+ end
5
+
6
+ guard 'minitest' do
7
+ watch(%r|^test/unit/test_(.*)\.rb|)
8
+ watch(%r|^lib/*\.rb|){'test/unit'}
9
+ watch(%r|^lib/.*/*\.rb|){'test/unit'}
10
+ watch(%r{^lib/.*/([^/]+)\.rb$}){|m| "test/unit/test_#{m[1]}.rb"}
11
+ watch(%r|^test/helper\.rb|){'test/unit'}
12
+ end
data/LICENSE.txt CHANGED
@@ -1,20 +1,20 @@
1
- Copyright (c) 2011 Nicolas E. Rabenau
2
-
3
- Permission is hereby granted, free of charge, to any person obtaining
4
- a copy of this software and associated documentation files (the
5
- "Software"), to deal in the Software without restriction, including
6
- without limitation the rights to use, copy, modify, merge, publish,
7
- distribute, sublicense, and/or sell copies of the Software, and to
8
- permit persons to whom the Software is furnished to do so, subject to
9
- the following conditions:
10
-
11
- The above copyright notice and this permission notice shall be
12
- included in all copies or substantial portions of the Software.
13
-
14
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
15
- EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
16
- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
17
- NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
18
- LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
19
- OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
20
- WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
1
+ Copyright (c) 2011-2014 Nicolas E. Rabenau
2
+
3
+ Permission is hereby granted, free of charge, to any person obtaining
4
+ a copy of this software and associated documentation files (the
5
+ "Software"), to deal in the Software without restriction, including
6
+ without limitation the rights to use, copy, modify, merge, publish,
7
+ distribute, sublicense, and/or sell copies of the Software, and to
8
+ permit persons to whom the Software is furnished to do so, subject to
9
+ the following conditions:
10
+
11
+ The above copyright notice and this permission notice shall be
12
+ included in all copies or substantial portions of the Software.
13
+
14
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
15
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
16
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
17
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
18
+ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
19
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
20
+ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
@@ -1,171 +1,185 @@
1
- Dropcaster - Simple Podcast Publishing with Dropbox
2
- ===================================================
3
- [Dropcaster](http://nerab.github.com/dropcaster) is a podcast feed generator for the command line. It is most simple to use with Dropbox, but works equally well with any other hoster.
4
-
5
- Author: Nicolas E. Rabenau <nerab@gmx.at>
6
-
7
- What is the problem Dropcaster is trying to solve?
8
- ==================================================
9
- You have a number of podcast episodes that you would like to publish as a feed. Nothing else - no fancy website, no stats, nothing but the pure podcast.
10
-
11
- With Dropcaster, you simply put the mp3 files into the Public folder of your [Dropbox](http://www.dropbox.com/). Then run the Dropcaster script that generates the feed, writing it to a file in your Dropbox, e.g. index.rss. All mp3 files in the Public folder of your Dropbox are already accessible via HTTP, and so will the RSS file. You can then take the RSS file's URL and publish it (again, this is because any file in the Public folder of a Dropbox automatically gets a public, HTTP-accessible URL).
12
-
13
- The feed URL can be consumed by any podcatcher, e.g. [iTunes](http://www.apple.com/itunes/) or [Juice](http://juicereceiver.sourceforge.net/).
14
-
15
- Installation
16
- ============
17
- To get started, use RubyGems to install Dropcaster:
18
-
19
- $ gem install dropcaster
20
-
21
- With Dropcaster installed, you can use the `dropcaster` command to generate a new podcast feed document.
22
-
23
- Basic Usage
24
- ===========
25
- Once Dropcaster is installed, the only two other things you will need are a channel definition and one or more mp3 files to publish.
26
-
27
- Let's start with the channel definition. It is a simple [YAML](http://yaml.org/) file that holds the general information about your podcast channel. According to the [RSS 2.0 spec](http://feedvalidator.org/docs/rss2.html#requiredChannelElements), the only mandatory information that your channel absolutely needs are a title, a description and a link to a web site where the channel belongs to.
28
-
29
- The simplest channel file looks like this:
30
-
31
- :title: 'All About Everything'
32
- :subtitle: 'A show about everything'
33
- :url: 'http://www.example.com/podcasts/everything/index.html'
34
-
35
- Store this file as channel.yml in the same directory where the mp3 files of your podcast reside. The channel definition is expected to be present in the same directory as your mp3 files, but this can be overridden using a command line switch. You can find a [more elaborate example](http://github.com/nerab/dropcaster/blob/master/doc/sample-channel.yml) for the channel definition in the doc folder of the Dropcaster gem. You can find it by running `gem open dropcaster`.
36
-
37
- Now that we have the podcast channel defined, we need at least one episode (an audio file) in it. From Dropcaster's perspective, it does not matter how the episode was produced, but the critical information is the meta data in the mp3 file, because that is the authoritative source for the episode information. Almost all audio editors can write metadata, usually called ID3 tags. Dropcaster reads these tags from the mp3 files and fills the item element in the feed (that's how an episode is defined, technically) from it.
38
-
39
- With all required pieces in place, we could generate the podcast feed. Just before we do that, we will inspect the feed by running the following commands:
40
-
41
- $ cd ~/Dropbox/Public
42
- $ dropcaster
43
-
44
- (The above lines assume that you are using Dropbox, and that there is at least one mp3 file in ~/Dropbox/Public).
45
-
46
- Dropcaster will print the feed to standard-out, without writing it to disk. When you are happy with the results, call Dropcaster again, but redirect the output to a file, this time:
47
-
48
- $ dropcaster > index.rss
49
-
50
- If all went well, you will now have a valid podcast feed in your Dropbox, listing all mp3 files as podcast episodes. Please see the section [Publish Your Feed] for details on how to find the public URL of your feed.
51
-
52
- Use Cases
53
- =========
54
- Publish a New Episode
55
- ---------------------
56
- 1. Drop the mp3 file into the Dropbox Public folder (e.g. ~/Dropbox/Public), and then run the following command in the directory where the mp3 files reside:
57
-
58
- $ dropcaster > index.rss
59
-
60
- 1. Dropbox will sync the updated index.rss file to its web server and any podcast client will download the new episode as soon as it has loaded the updated index.rss.
61
-
62
- Delete an Episode
63
- -----------------
64
- Remove the mp3 you want to delete from the Dropbox Public folder, and then run the following command in the directory where the remaining mp3 files reside:
65
-
66
- $ dropcaster > index.rss
67
-
68
- Replace an Episode With an Updated File
69
- ---------------------------------------
70
- In the Dropbox Public folder, replace the mp3 you want to update with a new version, and then run the following command in the directory where the mp3 files reside:
71
-
72
- $ dropcaster > index.rss
73
-
74
- Publish Your Feed
75
- -----------------
76
- 1. Re-generate the feed to make sure the it is up to date (see above):
77
-
78
- $ dropcaster > index.rss
79
-
80
- 1. In your Dropbox Public folder, right-click the index.rss and select "Dropbox / Copy public link". This copies the public, HTTP-addressable link to your podcast into the clipboard.
81
- 1. Publish this link and tell people to subscribe to it.
82
-
83
- Generate a Podcast Feed for a Subset of the Available MP3 Files
84
- ---------------------------------------------------------------
85
- Dropcaster accepts any number of files or directories as episodes. For directories, all files ending in .mp3 will be included. For advanced filtering, you can use regular shell patterns to further specify which files will be included. These patterns will be resolved by the shell itself (e.g. bash), and not by Dropcaster.
86
-
87
- For example, in order to generate a feed that only publishes MP3 files where the name starts with 'A', call Dropcaster like this:
88
-
89
- $ dropcaster A*.mp3 > index.rss
90
-
91
- Publish More than One Feed
92
- --------------------------
93
-
94
- $ dropcaster project1 > project1.rss
95
- $ dropcaster project2 > project2.rss
96
-
97
- or
98
-
99
- $ cd project1
100
- $ dropcaster > index.rss
101
- $ cd ../project2
102
- $ dropcaster > index.rss
103
-
104
- Include Episodes From Two Subdirectories Into a Single Feed
105
- -----------------------------------------------------------
106
-
107
- $ dropcaster project1 project2 > index.rss
108
-
109
- Advanced features
110
- =================
111
- Overriding defaults
112
- -------------------
113
- Dropcaster is opinionated software. That means, it makes a number of assumptions about names, files, and directory structures. Dropcaster will be most simple to use if these assumptions and opinions apply to your way of using the program.
114
-
115
- However, it is still possible to override Dropcaster's behavior in many ways. You can, for instance, host your episode files on a different URL than the channel. Instead of writing title, subtitle, etc. to a channel.yml, you may also spedify them on the command line.
116
-
117
- In order to find out about all the options, simply run
118
-
119
- $ dropcaster --help
120
-
121
- Using custom channel templates
122
- ------------------------------
123
- Dropcaster generates a feed that is suitable for most podcast clients, especially iTunes. It is also possible to customize the channel by supplying an alternative channel template on the command line. Start your own template by copying the default template, or look at the test directory of the dropcaster gem. You can get there by running `gem open dropcaster`.
124
-
125
- Sidecar files
126
- -------------
127
- You may override the meta data for any episode by providing a YAML file with the same name as the mp3 file, but with an extension of yml or yaml (ususally refered to as [sidecar file](http://en.wikipedia.org/wiki/Sidecar_file)). Any attributes specified in this file override the ID tags in the mp3 file.
128
-
129
- Dropcaster will only write the sidecar file if the appropriate command line option was passed, and it will use the information in it only for generating new files like the index.rss. It will not write back to mp3 files.
130
-
131
- A Note on iTunes
132
- ----------------
133
- The generated XML file contains all elements required for iTunes. However, Dropcaster will not notify the iTunes store about new episodes.
134
-
135
- Using Dropcaster Without Dropbox
136
- --------------------------------
137
- The whole concept of Dropcaster works perfectly fine without Dropbox. Just run the Dropcaster script in a directory of mp3 files and upload the files as well as the generated index.rss to a web server. Leave the relative position of the index and mp3 files as is, otherwise the path to the mp3 files in index.rss will become invalid.
138
-
139
- Episode Identifier (uuid)
140
- -------------------------
141
- Dropcaster uses a rather simple approach to uniquely identify the episodes. It simply generates a SHA1 hash of the mp3 file. If it changes, for whatever reason (even if only a tag was changed), the episode will get a new UUID, and any podcatcher will fetch the episode again (which is what you want, in most cases).
142
-
143
- Modifying the sidecar file does not change the UUID, because it only affects the feed and not the episode itself.
144
-
145
- I Don't Like the Output Format that Dropcaster produces
146
- -------------------------------------------------------
147
- Dropcaster uses an ERB template to generate the XML feed. The template was written so that it is easy to understand, but not necessarily in a way that would make the output rather nice-looking. That should not be an issue, as long as the XML is correct.
148
-
149
- It you prefer a more aesthetically pleasing output, just pipe the output of Dropcaster through `xmllint`, which is part of [libxml](http://xmlsoft.org/), which in turn is one of the prerequisites of the Dropcaster gem, and, as such, installed with Dropcaster):
150
-
151
- dropcaster | xmllint --format -
152
-
153
- For writing the output to a file, just redirect the ouput of the above command:
154
-
155
- dropcaster | xmllint --format - > index.rss
156
-
157
- Contributing to Dropcaster
158
- ==========================
159
- Dropcaster is hosted at [Github](http://github.com/nerab/dropcaster):
160
-
161
- * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
162
- * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
163
- * Fork the project
164
- * Start a feature/bugfix branch
165
- * Commit and push until you are happy with your contribution
166
- * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
167
- * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
168
-
169
- Copyright
170
- =========
171
- Copyright (c) 2011 Nicolas E. Rabenau. See LICENSE.txt for further details.
1
+ # Dropcaster - Simple Podcast Publishing with Dropbox
2
+
3
+ [![Build Status](https://travis-ci.org/nerab/dropcaster.png?branch=master)](https://travis-ci.org/nerab/dropcaster)
4
+
5
+ [Dropcaster](http://rubydoc.info/gems/dropcaster/file/README.md) is a podcast feed generator for the command line. It is most simple to use with Dropbox, but works equally well with any other hoster.
6
+
7
+ Author: Nicolas E. Rabenau <nerab@gmx.at>
8
+
9
+ # What is the problem Dropcaster is trying to solve?
10
+
11
+ You have a number of podcast episodes that you would like to publish as a feed. Nothing else - no fancy website, no stats, nothing but the pure podcast.
12
+
13
+ With Dropcaster, you simply put the mp3 files into the Public folder of your [Dropbox](http://www.dropbox.com/). Then run the Dropcaster script that generates the feed, writing it to a file in your Dropbox, e.g. index.rss. All mp3 files in the Public folder of your Dropbox are already accessible via HTTP, and so will the RSS file. You can then take the RSS file's URL and publish it (again, this is because any file in the Public folder of a Dropbox automatically gets a public, HTTP-accessible URL).
14
+
15
+ The feed URL can be consumed by any podcatcher, e.g. [iTunes](http://www.apple.com/itunes/) or [Juice](http://juicereceiver.sourceforge.net/).
16
+
17
+ # Installation
18
+
19
+ To get started, use RubyGems to install Dropcaster:
20
+
21
+ $ gem install dropcaster
22
+
23
+ With Dropcaster installed, you can use the `dropcaster` command to generate a new podcast feed document.
24
+
25
+ # Basic Usage
26
+
27
+ Once Dropcaster is installed, the only two other things you will need are a channel definition and one or more mp3 files to publish.
28
+
29
+ Let's start with the channel definition. It is a simple [YAML](http://yaml.org/) file that holds the general information about your podcast channel. According to the [RSS 2.0 spec](http://feedvalidator.org/docs/rss2.html#requiredChannelElements), the only mandatory information that your channel absolutely needs are a title, a description and a link to a web site where the channel belongs to.
30
+
31
+ The simplest channel file looks like this:
32
+
33
+ :title: 'All About Everything'
34
+ :subtitle: 'A show about everything'
35
+ :url: 'http://www.example.com/podcasts/everything/index.html'
36
+
37
+ Store this file as channel.yml in the same directory where the mp3 files of your podcast reside. The channel definition is expected to be present in the same directory as your mp3 files, but this can be overridden using a command line switch. You can find a [more elaborate example](http://github.com/nerab/dropcaster/blob/master/doc/sample-channel.yml) for the channel definition in the doc folder of the Dropcaster gem. You can find it by running `gem open dropcaster`.
38
+
39
+ Now that we have the podcast channel defined, we need at least one episode (an audio file) in it. From Dropcaster's perspective, it does not matter how the episode was produced, but the critical information is the meta data in the mp3 file, because that is the authoritative source for the episode information. Almost all audio editors can write metadata, usually called ID3 tags. Dropcaster reads these tags from the mp3 files and fills the item element in the feed (that's how an episode is defined, technically) from it.
40
+
41
+ With all required pieces in place, we could generate the podcast feed. Just before we do that, we will inspect the feed by running the following commands:
42
+
43
+ $ cd ~/Dropbox/Public
44
+ $ dropcaster
45
+
46
+ (The above lines assume that you are using Dropbox, and that there is at least one mp3 file in ~/Dropbox/Public).
47
+
48
+ Dropcaster will print the feed to standard-out, without writing it to disk. When you are happy with the results, call Dropcaster again, but redirect the output to a file, this time:
49
+
50
+ $ dropcaster > index.rss
51
+
52
+ If all went well, you will now have a valid podcast feed in your Dropbox, listing all mp3 files as podcast episodes. Please see the section [Publish Your Feed] for details on how to find the public URL of your feed.
53
+
54
+ # Use Cases
55
+
56
+ ## Publish a New Episode
57
+
58
+ 1. Drop the mp3 file into the Dropbox Public folder (e.g. ~/Dropbox/Public), and then run the following command in the directory where the mp3 files reside:
59
+
60
+ $ dropcaster > index.rss
61
+
62
+ 1. Dropbox will sync the updated index.rss file to its web server and any podcast client will download the new episode as soon as it has loaded the updated index.rss.
63
+
64
+ ## Delete an Episode
65
+
66
+ Remove the mp3 you want to delete from the Dropbox Public folder, and then run the following command in the directory where the remaining mp3 files reside:
67
+
68
+ $ dropcaster > index.rss
69
+
70
+ ## Replace an Episode With an Updated File
71
+
72
+ In the Dropbox Public folder, replace the mp3 you want to update with a new version, and then run the following command in the directory where the mp3 files reside:
73
+
74
+ $ dropcaster > index.rss
75
+
76
+ ## Publish Your Feed
77
+
78
+ 1. Re-generate the feed to make sure the it is up to date (see above):
79
+
80
+ $ dropcaster > index.rss
81
+
82
+ 1. In your Dropbox Public folder, right-click the index.rss and select "Dropbox / Copy public link". This copies the public, HTTP-addressable link to your podcast into the clipboard.
83
+ 1. Publish this link and tell people to subscribe to it.
84
+
85
+ ## Generate a Podcast Feed for a Subset of the Available MP3 Files
86
+
87
+ Dropcaster accepts any number of files or directories as episodes. For directories, all files ending in .mp3 will be included. For advanced filtering, you can use regular shell patterns to further specify which files will be included. These patterns will be resolved by the shell itself (e.g. bash), and not by Dropcaster.
88
+
89
+ For example, in order to generate a feed that only publishes MP3 files where the name starts with 'A', call Dropcaster like this:
90
+
91
+ $ dropcaster A*.mp3 > index.rss
92
+
93
+ ## Publish More than One Feed
94
+
95
+ $ dropcaster project1 > project1.rss
96
+ $ dropcaster project2 > project2.rss
97
+
98
+ or
99
+
100
+ $ cd project1
101
+ $ dropcaster > index.rss
102
+ $ cd ../project2
103
+ $ dropcaster > index.rss
104
+
105
+ ## Include Episodes From Two Subdirectories Into a Single Feed
106
+
107
+ $ dropcaster project1 project2 > index.rss
108
+
109
+ # Advanced features
110
+
111
+ ## Overriding defaults
112
+
113
+ Dropcaster is opinionated software. That means, it makes a number of assumptions about names, files, and directory structures. Dropcaster will be most simple to use if these assumptions and opinions apply to your way of using the program.
114
+
115
+ However, it is still possible to override Dropcaster's behavior in many ways. You can, for instance, host your episode files on a different URL than the channel. Instead of writing title, subtitle, etc. to a channel.yml, you may also spedify them on the command line.
116
+
117
+ In order to find out about all the options, simply run
118
+
119
+ $ dropcaster --help
120
+
121
+ ## Using custom channel templates
122
+
123
+ Dropcaster generates a feed that is suitable for most podcast clients, especially iTunes. By default, dropcaster follows [Apple's podcast specs / recommendations](http://www.apple.com/itunes/podcasts/specs.html).
124
+
125
+ It is also possible to customize the channel by supplying an alternative channel template on the command line. Start your own template by copying the default template, or look at the test directory of the dropcaster gem. You can get there by running `gem open dropcaster`.
126
+
127
+ ## Generate a HTML page for your podcast
128
+
129
+ Besides generating an RSS feed, dropcaster can also generate HTML that can be used as a home page for your podcast. The template directory contains a sample template that can be used to get started:
130
+
131
+ $ dropcaster --channel-template templates/channel.html.erb
132
+
133
+ As discussed above, the output of this command can be written to a file, too:
134
+
135
+ $ dropcaster --channel-template templates/channel.html.erb > ~/Dropbox/Public/allabouteverything.html
136
+
137
+ Dropcaster works exactly the same, whether it generates an RSS feed or a HTML page. Therefore, all options discussed before also apply when generating HTML.
138
+
139
+ ## Sidecar files
140
+
141
+ You may override the meta data for any episode by providing a YAML file with the same name as the mp3 file, but with an extension of yml or yaml (ususally refered to as [sidecar file](http://en.wikipedia.org/wiki/Sidecar_file)). Any attributes specified in this file override the ID tags in the mp3 file.
142
+
143
+ Dropcaster will only write the sidecar file if the appropriate command line option was passed, and it will use the information in it only for generating new files like the index.rss. It will not write back to mp3 files.
144
+
145
+ ## A Note on iTunes
146
+
147
+ The generated XML file contains all elements required for iTunes. However, Dropcaster will not notify the iTunes store about new episodes.
148
+
149
+ ## Using Dropcaster Without Dropbox
150
+
151
+ The whole concept of Dropcaster works perfectly fine without Dropbox. Just run the Dropcaster script in a directory of mp3 files and upload the files as well as the generated index.rss to a web server. Leave the relative position of the index and mp3 files as is, otherwise the path to the mp3 files in index.rss will become invalid.
152
+
153
+ ## Episode Identifier (uuid)
154
+
155
+ Dropcaster uses a rather simple approach to uniquely identify the episodes. It simply generates a SHA1 hash of the mp3 file. If it changes, for whatever reason (even if only a tag was changed), the episode will get a new UUID, and any podcatcher will fetch the episode again (which is what you want, in most cases).
156
+
157
+ Modifying the sidecar file does not change the UUID, because it only affects the feed and not the episode itself.
158
+
159
+ ## I Don't Like the Output Format that Dropcaster produces
160
+
161
+ Dropcaster uses an ERB template to generate the XML feed. The template was written so that it is easy to understand, but not necessarily in a way that would make the output rather nice-looking. That should not be an issue, as long as the XML is correct.
162
+
163
+ It you prefer a more aesthetically pleasing output, just pipe the output of Dropcaster through `xmllint`, which is part of [libxml](http://xmlsoft.org/), which in turn is one of the prerequisites of the Dropcaster gem, and, as such, installed with Dropcaster):
164
+
165
+ dropcaster | xmllint --format -
166
+
167
+ For writing the output to a file, just redirect the ouput of the above command:
168
+
169
+ dropcaster | xmllint --format - > index.rss
170
+
171
+ # Contributing to Dropcaster
172
+
173
+ Dropcaster is hosted at [Github](http://github.com/nerab/dropcaster):
174
+
175
+ * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
176
+ * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
177
+ * Fork the project
178
+ * Start a feature/bugfix branch
179
+ * Commit and push until you are happy with your contribution
180
+ * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
181
+ * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
182
+
183
+ # Copyright
184
+
185
+ Copyright (c) 2011-2014 Nicolas E. Rabenau. See [LICENSE.txt](https://raw.github.com/nerab/dropcaster/master/LICENSE.txt) for further details.