How we overcame the hosting challenges of our Moodle application
-Abirami S, Moodle Developer, Product team
As the team responsible for building internal applications, we wanted to improve codePannu’s training process. The content of our training team, e-learning team, and students was distributed across different platforms. This led to miscommunication, too much effort to onboard trainers, and difficulty in maintaining content consistency. To address these challenges, my team decided to build a Learning Management System (LMS) that would bring together our training team, e-learning content team, and students in one common platform. After much deliberation, we selected Moodle to build our Learning Management System (LMS). Moodle’s widespread adoption, open-source nature, and supportive community made it the ideal choice for our needs.
The Search for the Perfect Host
We installed Moodle on our local machines, explored features and built the prototype of the LMS. The next step was to find a suitable provider to host our application. We wanted a solution that was:
- Quick load time for optimal user experience.
- Customizable to suit our technical requirements.
- Affordable to accommodate our initial budget.
- Scalable as per the growing needs of our organization.
- Reliable with very minimal downtime to avoid disruptions.
As a Moodle developer, I took the initiative to explore various hosting options and assess their suitability for our LMS. During my exploration journey, I experimented with three different hosting providers before I found our ideal match, each offering unique experiences and lessons learned.
Hostinger: A False Start
My initial attempt was with Hostinger as we had already hosted a couple of other internal applications on their server. Our hosting plan included a Virtual Private Server (VPS) that was fast, reliable and customizable. Hostinger also provided affordable hosting plans and excellent customer service. However, our Virtual Private Server (VPS) plan did not come with a cPanel for easy installations. Hence, our Moodle developers will have to use the Ubuntu command line, to install the technical requirements and then host the LMS. I understood that this would be a hurdle due to our team’s limited experience with Ubuntu and it’s command-line. So I decided to explore other alternatives.
RedServer: A Missed Opportunity
Next, I explored RedServer for its affordable pricing and exceptional customer support. I was impressed by the cPanel and easy installation process. With great delight, I progressed with the installation, but encountered an unexpected compatibility issue. The PHP version required for our Moodle application was not supported by RedServer at the time. This setback again forced me to look for more providers.
A glimpse of hope: Our third provider
Undeterred, I found a local provider through my network, who provided affordable pricing, easy-to-use cPanel, and PHP and MySQL versions suitable for our requirements. Our product team instantly adapted the platform, hosted our LMS and announced it to the rest of the organization. Our training and E-learning content team were delighted by its ability to streamline class exercises, assignments, and preview materials. This centralized LMS saved them valuable time, enhanced their productivity and help easily guide our students to the course content.
Unfortunately, this promising partnership was short-lived. While we were excited that the provider gave all the features we wanted, we overlooked critical factors like uptime and customer support. Within a few months, frequent, unannounced downtime plagued our service, causing significant disruptions for our users.
By now, our platform had been adapted organization wide, by tens of trainers and hundreds of students. We had transitioned from exploration phase to full scale adoption. Downtime was no longer an option, as it would severely impact many teams. Our training team struggled to conduct sessions, and our e-learning team faced delays in their deadlines to upload content. We also received unsatisfactory answers regarding the down time and lacked reassurance about preventing future occurrences. One particular day, while being severely impacted by a downtime that lasted many hours, I gave up and started looking for another provider.
Finding Our Ideal Host: A2 Hosting
Recognizing our critical need for reliability, scalability and support, I made the decision to migrate to A2 Hosting, a premium hosting provider. They offered all the features we were looking for, along with exceptional customer service. As we already had a clean backup of our data, we were able to migrate our Moodle application overnight. Since migration, things has been great. Their proactive approach to help us resolve issues has exceeded our expectations. They even worked hand in hand with my team to resolve various technical challenges within Moodle, beyond the scope of hosting. Impressed by their performance, we also moved our Moodle development environment to the same provider.
Lessons Learned and Best Practices
Through our experiences, we’ve gained valuable insights into hosting Moodle effectively:
- Invest time to conduct thorough research on many hosting providers to ensure they meet Moodle’s specific requirements.
- Prioritize choosing a provider with a proven record of reliability and excellent customer support.
- Implement a robust backup strategy to safeguard your data and enable swift recovery in case of unforeseen incidents.
- Keep a close eye on your server’s performance and address any issues promptly.
By sharing these insights, I aim to assist other Moodle administrators in making informed decisions and avoiding common pitfalls during hosting.