HistoryAtOurHouse Back End
Switched to a CMS to manage content instead of a hand coded approach. An eCommerce solution was also set up to handle orders automatically instead of having to grant access manually to each customer.
Historyatourhouse.com is an online education company dedicated to teaching history to homeschoolers and adults via live and recorded lectures. The owner originally needed help to fix webpages and to make files available in different formats. When I first joined the team that worked on the website, we were tasked with the job of converting files, specifically ARF to MP4.
This wasn’t any file conversion but a bulk file conversion with 1000+ files to be converted. An interface that only had a one-file-at-a-time method was the only way to convert the files initially. I realized this was no way to convert files because it takes too much time. I needed to figure out how to bulk-convert the files. So I looked online until found a VBS script that completed the task. Unfortunately it offered no configurability. I took that script and rewrote it as a shell script with the required settings to convert the files. In a future version I will add more configurability for the file conversion process. Currently all we have to do is move our files to a directory and run the shell script to convert them.
After the MP4 files were created some of them needed to be linked in web pages. So, I and a team member edited the HTML to show that. We were running out of disk space and even went over the max so the owner asked me to come up with a way to cut space usage.
I noticed that some MP3 files could be optimized for better space usage (because it was only speech) and made some samples for him to check. After he chose the lowest acceptable bit rate I started bulk converting the MP3s to a lower bit rate for reduced size. In all I had reduced storage requirements from ~290GB to ~250GB.
multiple times, thus automating the system. The new system is essentially hands free. The eCommerce system creates the user accounts and grants access to certain pages that create the authentication cookie and gives a link to the content. After the authentication cookie is created then the user has access to the content that they purchased.