Release Management

I can see that I need to do something about the get_enclosures release management. Yesterday the 0.2 version was downloaded 50 times, while the 0.3 was downloaded 11 times. That’s not good, so I really need to do something ASAP. I guess in the short term, I’ll just remove the links to old versions and make them point to the new one, but I don’t want to have to update every old post every time I release one. Someone suggested that I just link to a release directory rather than to individual files, which is a good idea. My problem is that at the top level I have my Apache setup configured via .htaccess to serve the weblog page as the index. Does anyone know how to override that at a lower level? I want to have a subdirectory not serve that out, instead giving a directory listing. I looked at the Apache docs last night, seeing how I could turn that off or make the DirectoryIndex directive in my .htaccess file not recurse, and couldn’t figure it out.

Published by


Dave Slusher is a blogger, podcaster, computer programmer, author, science fiction fan and father. Member of the Podcast Hall of Fame class of 2022.

4 thoughts on “Release Management”

  1. bernard Flach says:

    The anwser is SourceForge .. Just like the iPodder project.

  2. The answer is SourceForge … just like the iPodder project

  3. Chris C. says:

    Can’t you just put an .htaccess file in the subdirectory to override the problematic setting that’s recursing down? Sorry if I’m misunderstanding the problem …

  4. S. Das says:

    Option -Indexes

    I think that is what you want. That will turn off the directory indexing. You can also simply turn that off in the apache config, and then put

    Option Indexes

    into a .htaccess file in the directory you want indexed.

Comments are closed.