February 11, 2013

Updating Bugify on cPanel and other hosts that require htdocs or public_html etc

Some web hosting control panels require that your publicly accessible folder for your website be named “public_html” or “htdocs” (or whatever).  In the past, this has been a bit annoying with Bugify because we have a folder called “public”, that we expect your web server config to point to (the “public” folder is the only folder that should be publicly accessible – the others should be outside the document root).

Generally, if you don’t have SSH access to create a symlink from “public_html” (or whatever) to “public”, then you would rename the Bugify “public” folder to the folder name that your hosting control panel requires.  This is fine, and Bugify still works fine like this… up to a point.

Where Bugify failed with this type of setup, is the auto-update system.  In the past, when you use the auto-update system, Bugify would actually create a new folder called “public” and copy the new public files into it, rather than using your “public_html” (or whatever) folder.

From v1.5, the update system will be a little smarter, and will handle that automatically for you.  So if you’re running Bugify from a folder other than “public”, the auto-update system will work out the correct folder, and copy the new public files there.

It is very important to note that the change will only take effect for updates after the first release in 1.5.  So, when you update to v1.5, if you’re using a folder other than “public”, you will need to copy the new files over.  You won’t have to worry about whether or not this is you, because we’re going to check for you, and let you know 🙂

Leave a Reply