bitweaver
Wiki
wiki Home
List Pages
wiki Books
Orphan Pages
wiki Rankings
Photos
List Galleries
Forums
Browse forums
Files
List Galleries
Categories
List Categories
Sign In
Message Boards
»
08. Support - General talk
Newest
Oldest
Threaded
5
10
20
50
100
All
Messages
Reinstalling Bitweaver
Post Reply
Stephen Winters
Joined: 22 May 2005
Reinstalling Bitweaver
Posted:23 Jul 2005 (14:27 UTC)
xing
Joined: 07 Mar 2004
Posted:23 Jul 2005 (20:44 UTC)
Stephen Winters
Joined: 22 May 2005
Posted:24 Jul 2005 (18:49 UTC)
xing
Joined: 07 Mar 2004
Posted:25 Jul 2005 (08:27 UTC)
Stephen Winters
Joined: 22 May 2005
Thanks xing!
Posted:26 Jul 2005 (02:33 UTC)
Post Reply
Page 1 of 1
1
Post
Title
Login
If you are already registered, please enter your login credentials.
Your Name
Anonymous Post
Content Format
Tiki Wiki Syntax
Allow HTML
{quote format_guid="bbcode" comment_id="5606" user="xing"}i have never used Cpanel and i can't really help you much on that side. as for the original config_inc.php file, it might still be there, if you didn't delete any folders before uploading it to your server. here is a copy of a default config_inc.php file which you can use a template. once you have inserted the information as required, you can upload it to your server and your old bitweaver should be available. (make sure to give read/write access to temp/ and storage/) the variables needed to run bitweaver and which can be set during installation are these: [code:1:56e4e25813] <?php $gBitDbType = "postgres"; $gBitDbHost = "localhost"; $gBitDbUser = "username"; $gBitDbPassword = "password"; $gBitDbName = "databasename"; ?> [/code:1:56e4e25813] here is the full file: [code:1:56e4e25813] <?php // +----------------------------------------------------------------------+ // | Copyright (c) 2004, bitweaver.org // +----------------------------------------------------------------------+ // | All Rights Reserved. See copyright.txt for details and a complete list of authors. // | Licensed under the GNU LESSER GENERAL PUBLIC LICENSE. See license.txt for details // +----------------------------------------------------------------------+ // The following line is required and should not be altered global $gBitDbType, $gBitDbHost, $gBitDbUser, $gBitDbPassword, $gBitDbName, $smarty_force_compile, $gDebug, $gPreScan; // bitweaver can store its data in multiple different back ends. Currently we // support MySQL, MSSQL, Firebird, Sybase, PostgreSQL and Oracle. // Enter the hostname where your database lives, and the username and // password you use to connect to it. // // You must specify the name of a database that already exists. bitweaver will // not create the database for you, because it's very difficult to do that in // a reliable, database-neutral fashion. The user that you use should have // the following permissions: // // SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP // // The possible database types that we support are: // mysql Standard MySQL // sqlite SQLLite // mssql MS-SQL (experimental) // postgres PostgreSQL 7.x // oci8po Oracle (9i and newer) // firebird FireBird // sybase Sybase $gBitDbType = "postgres"; // Hostname or IP for your database. // Some examples: // 'localhost' if you are running the database on the same machine as bitweaver // If you use Oracle, insert your TNS Name here // If you use SQLite, insert the path and filename to your database file $gBitDbHost = "localhost"; // Database username $gBitDbUser = "username"; // Database password $gBitDbPassword = "password"; // Database name $gBitDbName = "databasename"; // This prefix will be prepended to the begining of every table name to allow multiple // independent installs to share a single database. By ending the prefix with a '.' (period) // you can use a schema in systems that support it. backticks '`' around the '.' are required if present // a schema example is: 'bit`.`' define( 'BIT_DB_PREFIX', '' ); // This is the path from the server root to your bitweaver location. // i.e. if you access bitweaver as 'http://MyServer.com/applications/new/wiki/index.php' // you should enter '/applications/new/' define( 'BIT_ROOT_URL', '/' ); // If you wish to force compiling of every page, you can set the next setting to // TRUE. this will, however, severly impact performance since every page that is // generated is generated afresh and the cache is recreated every time. $smarty_force_compile = FALSE; // This statement will enable you to view all database queries made //$gDebug = TRUE; // This will turn on ADODB performance monitoring and log all queries. This should // not be enabled except when doing query analysis due to an overall performance drop. // see kernel/admin/db_performance.php for statistics //define( 'DB_PERFORMANCE_STATS', TRUE ); // $gPreScan can be used to specify the order in which packages are scanned by the kernel. // In the example provided below, the kernel package is processed first, followed by the users and liberty packages. // Any packages not specified in $gPreScan are processed in the traditional order //$gPreScan = array( 'kernel', 'users', 'liberty' ); // if you set AUTO_BUG_SUBMIT to TRUE, the application will know that this site is running live and is not used for testing purposes. // This will prevent any horrible error pages from appearing and will redirect the user to a 'nicer' error page and // will automatically email the team with details regarding the error. // Bugs added to http://www.sourceforge.net will get processed faster since more people have access to these. define( 'AUTO_BUG_SUBMIT', FALSE ); ?> [/code:1:56e4e25813] xing{/quote}
Recent Page Changes
welcome to bitweaver.org
Bitweaver Overview
ReleaseTwo Schema Changelog 2006
PressReleaseOne
Spider's Web
Press Release Two
BitcommercePackage
InfiniBand vs Ethernet Performance
InfiniBand for Dummies
Show More…