Home
WIZARDISHUNGRY edited this page Sep 12, 2010
·
42 revisions
Welcome to the sflimetracker wiki! You should probably look at the JIRA issue tracker or the QuickStart! The project wiki for the LimeCast may be of interest as well. There’s also a list of open questions if you feel interested enough. A user created a list of user questions.
Please see the QuickStart for install instructions.
- 0.11 – 18 Mar 2009 – MD5 = 6334ea6788527789ce059ad5ba192a99 SHA1 = 123ac4f01bf25cc90c433441222b277d1e2a456e
- 0.10 – 10 Mar 2009 – MD5 = c7725b14dfbe4aa7e19c9ede5d6e5d45 SHA1 = 7c579a8ed9bd0b1b7c99cace597e14ff25acd498
- 0.09 – 6 Mar 2009 – MD5 = 692a7c4fae269d8c58d2071421975b47 SHA1 = 6c23f821cf9e375709e0eecd2663cd3b0cfaaf85
-
dev version on DreamHost – password is
x; please don’t be stupid.
The features for sfLimeTracker are:
- Easy to install: The user can just ftp a bunch of files to a shared web host account. I think we can assume the user has access to phpMyAdmin, but probably doesn’t have shell access.
- Web interface: Navigate to it, set an admin password, log in.
- Feeds: Supports multiple feeds and sets of feeds. For instance, a video podcast might have one feed with content in Windows Media, while another with the same shows but encoded in H.264.
- BitTorrent Tracker: It’s a BitTorrent tracker.
- Makes Torrent: The user can make a torrent of a file using the url. LimeCast hashes the file, and creates a .torrent.
- Download a .zip file
- Unzip it on your personal computer
- Upload the folder of files to your web host
- Navigate your browser to install.php, where you will set the administrator password and enter the control panel
- make a feed
- fill out all the feed metadata
- feed settings, like when to retire episodes
- post a new episode in a variety of formats, fill out metadata
- make a link for a single file, outside of a feed
- create torrents by url to file or a torrent
- progressive hashing
- upstream feed, a feed from wordpress, etc.
- remove links, episodes, and feeds
- log out, change password
- 0.08 – 3 Mar 2009 – MD5 = 6124dc243ed88cba276590cb23d5be65 SHA1 = 1c2eaf41b91e919c6b0858007c421be0ad8a73a3
- 0.07 – 25 Feb 2009 – MD5 = c2171b16d871975308de2b3d12a3dc1f SHA1 = b1e74995b151cf5d40207c2a3b5e9a367c6f6cb3
- 0.061 – 10 Feb 2009 – MD5 = 635dd7a81209cf1f505b6fe2c4784977 SHA1 = f2d33287ed038a07b7412bf037e907b916bf3dfe
- 0.06 – 5 Feb 2009 – MD5 = a6c1c32c98dcc5c016a9d60428903bea SHA1 = 1cf084604c915fc38205dcb2f622251d18c218ba
- 0.05 – 20 Jan 2009 – MD5 = bfd9663edcdfa5cd7a55135b175d1c22 SHA1 = 6f2121be2d42a894b806e7cfd91b760c2686d8cc
- 0.04 – 9 Jan 2009 – MD5 = 041f7699f0a3bd681634c018a255f879 SHA1 = ac1e18c843c7d2de97feefc7e18b14313412c163
- 0.03 – 9 Dec 2008 – MD5 = 1f1d05eb146588e099e6e50b84d0862b SHA1 = e8400d39b139343e4b83d9fbba5e31cc3d3c0848
- 0.02 – 7 Nov 2008 – MD5 = de6c5c01a42c067cff8a3bfd378db4d7 SHA1 = 4d4ebed6bfab9660e698be55f62ed9653a833ea1
- 0.01 – 21 Oct 2008 – MD5 = 13dca7953dab4467357d4a2177377ea1 SHA1 = b8da3141d3dbdfa1f92f999638f2f2b34de950fe