Setup database provider

来自Kooboo document

 

Kooboo CMS can almost support all the types of database, include the relational database and No-SQL database. Right now, we have implemented five types database provider for text content: XML, SQLCe, SQLServer, MySQL and MongoDB. 

XML

The xml provider is a configure-less, structure-less and simplest provider. It is the default provider include in the default release package.

The xml provider is also used on the site exporting/importing function. When exporting one site from the Kooboo CMS with non-default providers, the site will be exported as a site package using the default providers. When the site package being to import into a Kooboo CMS instance with non-default providers, it will convert the xml data into the specific database.

Highly recommended used in the development, do not used in the production.

 

SQLCe

provider is a relational database similar with . It is configure-less but have structure tables. Every sites in the same Kooboo CMS instance will has its owner standalone database file. It usually use in the site which each table with less than 50000 rows data. 

All the relational database[SQLCe,SQLServer, Mysql] have the same characteristic is they will always the dynamic tables for each content type, but it transparent to the users.

Usage:

• the Content_Providers.zip.
• Copy the files under "SQLCe" into the BIN folder of Kooboo CMS.

SQLServer

SQLServer provider have two modes: 

• Standalone mode. Each site will have its database file. In this mode, the user have to provide the "CreateDatabaseSetting" connection string which have create database permission. The site will using the connection setting in the "Connections" section.
• Shared mode. All the sites in the same instance will use the same database. In this mode, the user have to set "SharingDatabase" as "True", set the "SharingDatabaseConnectionString".

Usage:

• "Content_Providers.zip".
• Extract the zip file. Copy the files under "SQLServer" include "SQLServer.config" into BIN folder of Kooboo CMS..
• Create a new database or use the existing database, we call it "Kooboo CMS".
• Edit the "SQLServer.config" to specify the connection strings.

 
       
        
         
         
          Server=.\SQLExpress;Database=Kooboo_CMS; Trusted_Connection=Yes;
          
         
          Sample
          
         
        
       
        Server=.\SQLExpress;Database=Kooboo_CMS; Trusted_Connection=Yes;
        
       
        true
        
       
        Server=.\SQLExpress;Database=Kooboo_CMS; Trusted_Connection=Yes;
        
      

MySQL

MySQL provider usually used on MONO/*UNIX, and some shared web hosting do not support SQLServer.

Usage:

• "Content_Providers.zip".
• Extract the zip file. Copy the files under "MySQL" include "MySQL.config" into BIN folder of Kooboo CMS..
• Create a new database or use the existing database, we call it "Kooboo CMS".
• Edit the "MySQL.config" to specify the connection strings.

 
       
       
        Server=127.0.0.1;Database=Kooboo_CMS;Uid=root;Pwd=;charset=gbk;
        
       
        utf8
        
      

MangoDB

is a key-value database. It usually used in the site have a lot document but have few relations.

Usage:

• "Content_Providers.zip".
• Extract the zip file. Copy the files under "MySQL" include "MongoDB.config" into BIN folder of Kooboo CMS.
• the Mongodb server.
• Edit the "MongoDB.config" to specify the connection strings.

 
       
       
        mongodb://localhost
        
       
        false
        
      

Site migration between different Kooboo CMS instance with different providers

Migrating the site between different Kooboo CMS instances is a really great feature. For example: We can develop the site under the XML provider instance, but want to deploy the to another production instance with SQLServer. 

Usage:

1. Exporting the site from the old instance.
2. a new "Kooboo_CMS.zip".
3. Extract the "Kooboo_CMS.zip", doing some .
4. Setup the new web site on IIS.
5. Start the new web site, and importing the exported site.