Using SETUP in a production environment

POG SETUP has been designed to be used both in a testing and production environment. However, in a production enviroment, there are a few provisions:

Make sure you rename the setup folder to something harder to guess so that it won’t be accidentally “discovered” by anyone who shouldn’t gain such access to your data. For added protection, you can even password protect the setup directory using an .htaccess file:

Create a text file called .htpasswd and paste the following in it:
username:password

Replace username and password with your desired values.

Next, create a text file called .htaccess and paste the following in it:

AuthName “POG Setup”
AuthType Basic
AuthUserFile /full/path/to/.htpasswd
Require valid-user

Edit /full/path/to/.htpasswd to reflect the absolute path to the htpasswd. Finally, simply place the .htpasswd on your server and put the .htaccess file in the setup folder.

For more information on password protecting directories, you can ask Google

Also, please remember that each time you run SETUP, POG performs some unit tests on all your objects/tables; which means that some objects are inserted, updated, and deleted during the diagnostic phase. During that phase, we’ve made sure that SETUP deletes only those test objects and leaves any original data untouched. So, running SETUP on tables that already contain data should not cause any issues.

However, if you’re dealing with critical data that you absolutely cannot afford to lose, we’d strongly recommend that you back up your table(s) before running setup. In some extreme and unforeseen cases, something just might go wrong and we wouldn’t want you to lose any data because of POG. That would be totally uncool.