{"id":10964,"date":"2019-03-06T17:43:57","date_gmt":"2019-03-06T16:43:57","guid":{"rendered":"https:\/\/www.dsoverseas.com\/choosing-a-web-host-for-a-website-project\/"},"modified":"2026-04-18T23:43:02","modified_gmt":"2026-04-18T21:43:02","slug":"choosing-a-web-host-for-a-website-project","status":"publish","type":"post","link":"https:\/\/www.dsoverseas.com\/en\/choosing-a-web-host-for-a-website-project\/","title":{"rendered":"Choosing a web host for a website project"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text]<\/p>\n

Choosing a web host for a website project<\/h3>\n

It’s a case that began in January 2016, when our customer CORP<\/a>, entrusted us with the mission of redesigning its website, and the choice of host for a website project was put on the table.<\/p>\n

CORP had a very average version of its website, with the added bonus of hybrid hosting: domain name owned by Global Net, hosting by an alpha company (we’re withholding the name for reasons of professional ethics).<\/p>\n

At the start of our mission, we asked our customer for FTP access, the hosting manager and access to the database, but it turned out that the customer had no access and no information on this file. We began to approach the hosting company, which did everything in its power not to transmit the necessary information… it sounds bizarre, but nothing is bizarre when you consider what’s going to happen next! \"?\"<\/p>\n

We decided to limit the damage and contact Global Net, who already owned the domain name. We started by installing WP, and then the problems began … we spent more than 2 weeks going back and forth and trying to install our theme.<\/p>\n

After this period of great sorrow, we took the decision to migrate the hosting to OVH and to link the domain name to our new hosting. For the record, both the hosting and the beta version of the site took us about a week to complete.<\/p>\n

Our tips for choosing a web host<\/h4>\n

That’s how we advise our customers for this kind of job:<\/p>\n