The exported data then spends 10 to 15 seconds in your favorite editor where it undergoes the search and replace routine. Substitution of database prefix occurs in 863 edits. This occurrence is the actual number of tables in a single install event.
This number can be reduced substantially. My analysis and subsequent regret with this project was the lack of database prototyping before the final template was selected. Tables remain in this database that will never be used. This can be solved by editing the install files to generate a bare bones installation but consider this.
You will be selecting one of two choices regarding further prefix instantiation. If you start coding in the install files and sub-routines you will inevitably want to continue using the install routine to provoke your changes. The other choice I've already mentioned.
Time constraints considered the editor is far superior choice. Consider for some time the actual data entry required in the process. Consider the underlying protocols.
Data will have to be entered in the appropriate Zone file on your DNS server. At this time you have a list of table space names you are going to use. Consider how to cut copy and paste:
www.site1 IN CNAME site.com.
Efficiency and Quality are very important. Maintaining proper data now leads directly to less downtime in the site name order of events. Continue with your file manager now and create the directory structure you desire in the parameters folder. Consider how to best create this quickly.
At this point in the design a need arises to process the modules_var table quickly between sites on port 80. You can use your Web_Links module to link to the sites you will be editing in rapid succession by leaving one window open to the links and by clicking proceed to the new site --> admin --> settings and change the appropriate variables for the site.
I elected to use the jump box generation code that AlarConcepts provided for the project. Consider the data replication procedure carefully. Again creating a list of one hundred jump box links is best done with efficiency and quality.
Open you favorite editor once again. Open your httpd.conf file and reiterate your virtual host template. Consider the amount of data entry. You may want to use an include file in your httpd.conf. Efficiency and Quality are paramount in your data entry at this point. Replace and Paste quickly until all your selected domain concatenations are fulfilled.
Also on the sql side you have to consider the amount of data entry, Replace and Paste actions undergone. Personally I use vi transplanttable.sql through a shell and leave WordPad open with the data that undergoes Replacements. I leave it highlighted and quickly approve the all changes and copy text and one click drop into the INSERT buffer and move on changing the next as rapidly as the last.
So in conclusion we have to alter the Zone file, the httpd.conf file and the dump. Once this has occurred do mysql targetdatabase < reiteratedtables.sql and watch a dump of half a million lines slam your mysqld for as long as it wants to take.
Further database analysis will reveal number of tables present. I'm estimating around twenty-five thousand tables at present. Functionally your sites are live after the mysql import. Put the coffee on get busy.
Change the site names and make the sites user aware by providing data to the submit_news admin module and the settings module. These are the only two places I had to visit on a fresh install to change data. Consider changing even three different modules... Work quickly. The bots are coming.