tomster2300
01-19-2008, 01:22 AM
Alright, I'm not the most savvy about the technical wording on what I'm working on, so please bear with me.
I run the podcasting for the campus radio station in which I'm partially in charge. We just purchased webhosting with a new host, and are currently in the process of transferring our website and everything else to the new server. All of my podcast mp3s, xml generator software, and xml files are located on there as well, and have for the most part been transferred over successfully.
My podcasting process was to get the edited mp3s (recordings of previously broadcasted shows) from my staffers, upload them myself to the server via a free ftp client (ftp core lite), and then using a password protected xml generator built into the website (written by a previous staffer) I filled in the appropriate categories, and it published the xml feed. The program was nifty because it automatically posted the xml to our website along with a title, show host, description, etc. (all reading from the xml feed) as well as providing the xml link on the page for viewers to subscribe to via dragging and dropping the link into their player of choice.
This was all well and good, but we became backlogged since I was exclusively doing the uploading (and we have over 30 shows this semester), so I thought we could eliminate the ftp client and upload the files directly through the website through php. We found an open source xml generator on sourceforge which allowed php uploading, installed it onto our server, then found out our new webhost capped php uploads at around 7 mbs. My podcasts range from 20-70 mbs each, and I assume that the chances of their editing our .INI file to increase our cap are slim to none.
So, is there any other way we could upload without a ftp client? If we could, then staffers could upload their edited copies on their own, completely publish their own podcasts, and we could cut down on the backlog that has piled up.
EDIT: I know I could make everyone download the ftp client and use it, but that would mean handing over server login info to a staff of volunteers, which I'm not about to do. Php allowed staffers a way to put files up, but not be able to mess with them once they were loaded (I think at least). Because the staff is all volunteer based, I'm trying to make the entire podcasting process as simple and streamlined as possible to keep enthusiasm up. Too many hassles and people lose interest.
I run the podcasting for the campus radio station in which I'm partially in charge. We just purchased webhosting with a new host, and are currently in the process of transferring our website and everything else to the new server. All of my podcast mp3s, xml generator software, and xml files are located on there as well, and have for the most part been transferred over successfully.
My podcasting process was to get the edited mp3s (recordings of previously broadcasted shows) from my staffers, upload them myself to the server via a free ftp client (ftp core lite), and then using a password protected xml generator built into the website (written by a previous staffer) I filled in the appropriate categories, and it published the xml feed. The program was nifty because it automatically posted the xml to our website along with a title, show host, description, etc. (all reading from the xml feed) as well as providing the xml link on the page for viewers to subscribe to via dragging and dropping the link into their player of choice.
This was all well and good, but we became backlogged since I was exclusively doing the uploading (and we have over 30 shows this semester), so I thought we could eliminate the ftp client and upload the files directly through the website through php. We found an open source xml generator on sourceforge which allowed php uploading, installed it onto our server, then found out our new webhost capped php uploads at around 7 mbs. My podcasts range from 20-70 mbs each, and I assume that the chances of their editing our .INI file to increase our cap are slim to none.
So, is there any other way we could upload without a ftp client? If we could, then staffers could upload their edited copies on their own, completely publish their own podcasts, and we could cut down on the backlog that has piled up.
EDIT: I know I could make everyone download the ftp client and use it, but that would mean handing over server login info to a staff of volunteers, which I'm not about to do. Php allowed staffers a way to put files up, but not be able to mess with them once they were loaded (I think at least). Because the staff is all volunteer based, I'm trying to make the entire podcasting process as simple and streamlined as possible to keep enthusiasm up. Too many hassles and people lose interest.