If you are looking for JoomlaPack's Bleeding Edge repository of developer releases, it has been migrated to AkeebaBackup.com and is now called "Developer's Releases".The Bleeding Edge component was born out of the necessity for a zero-configuration file repository for Joomla!. Its mission was to host the development releases of JoomlaPack (and now Akeeba Backup). The major problem with the developer releases is that they are very frequently created and consist of many files. Trying to manage this kind of short lived releases with a traditional repository component such as DOCman, rokDownloads or Phoca Downloads proved to be a monumental task. For every directory and every file you have to click on a huge amount of configuration options to do as much as get it to be publicly available. It seemed quite reasonable to have a system where all I would have to do is upload the files. Period. No configuration, no nothing. What I needed was a "Zenpository", not a "repository". In other words, the software should be able to deduct the release name (software version) and produce a beautifully formatted Change Log without any further thinking or action on my part. Hence, the Bleeding Edge component was born.

Its key features - or, should I say, non-features - are:

• Doesn't have any configuration settings except the respository root's location, the title of the repository and a logo to display. Or just forget all about it and just set the repository root.
• Doesn't have an integrated flash / AJAX / PHP form upload system. You can upload your files with FTP or SCP. FileZilla Portable works much better than these half-arsed browser uploading methods anyway.
• Doesn't have flexibility in the repository structure. The root contains directories; one directory per displayed category / software title. Each category contains releases; one subdirectory per release. The subdirectory name is the release's version number. Each release contains files. Your visitors can download them. Nowhere else may you place files except in releases subdirectories. This is dead simple repository organization.
• Doesn't require clicking endless arrays of options and buttons to create directories. Just use your FTP or SCP client to create the bloody directory.
• Doesn't need clicking on a gazillion options per uploaded file just to make it publicly accessible. Just upload the file. I guess you wouldn't have uploaded it if you didn't want people to download it, right?
• Doesn't have ACL or any kind of access control. If you have uploaded a file it can be downloaded. If you need ACL, buy DOCman. If you need true ACL and make some cash out of it, buy AMBRA.subscriptions. If you don't give a damn about ACL, you're on the right spot.
• Doesn't keep any kind of statistics. Your server has this incredible thing called access logs. Duplicating its functionality is silly, stupid and suboptimal. Yet, for reasons unknown to me, everybody seems to do it. Whatever...
• It optionally parses a plain text file named CHANGELOG (all caps, no spaces, no extension) on each release subdirectory and displays its diff with the previous release in a beautiful format. Since this is a software releases repository, having a Change Log helps visitors understand if they should download your software.
• It does have a SEF router, though, for producing beautiful URLs.

Simple is better. Simple is beautiful. Narrowest scope works best.

In other words, it's the Zen of Joomla! repository components. It is designed to do exactly one (1) thing and do it efficiently. It is only meant for free software distribution. Nothing less, nothing more. It won't bother you with options. You'll either love it or hate it.

Love. Peace. May the GNU force be with you.