Why PHP developers should edit their files directly on the deployment server
This post is for php developers. And who use local servers like mysql and wamp to edit their backend code. Before uploading them to the deployment server.<p>The deployment server refers to the main server that powers your online website. It is not the server you use purposefully for debugging and nothing else.<p>I wrote this post because its good to see that, files behave in different ways on different servers.<p>Let&#x27;s dive into the ways php files are different on both local and deployment servers.<p>CHECK YOUR FILE NAMES. Wrong file names still work on mysql server but do not work on deployment server. For example, on mysql, &#x27;myfile.php&#x27; is the same as &#x27;myFile.php&#x27;. so &#x27;https:&#x2F;&#x2F;website.com&#x2F;myFile.php&#x27; is the same as &#x27;https:&#x2F;&#x2F;website.com&#x2F;myfile.php&#x27;
But on the deployment server, or your website host server, &#x27;myfile.php&#x27; is not the same as &#x27;myFile.php&#x27;. So if the link &#x27;https:&#x2F;&#x2F;website.com&#x2F;myFile.php&#x27; works, then the link &#x27;https:&#x2F;&#x2F;website.com&#x2F;myfile.php&#x27; will not work and vice versa.<p>Therefore, after testing your files on the local server, be sure to check the file names again before uploading them onto the deployment server.<p>In order to avoid all this work, why don&#x27;t you create and edit the files on the deployment server directly, so that you do know they work from the ground up.<p>This way, users can continue to access your website and your links while you edit them.