Loading...
 
Skip to main content

Architecture / Installation

Forum List Topic List

Forums » Architecture / Installation » Moving Tiki from one host to another
 
Thread actions
Print this page
  • Print all pages

    • Moving Tiki from one host to another

    Posted by vreebies posts: 3

    Hi, I am a total-newbie in this CMS scheme. But I am very interested in learning more about this groupware.

    Therefore, I am following step-by-step instructions just to get the DB started in my local PC at home (XP Pro, EasyPHP, Tiki 1.74).
    Once I am quite familiar with it, I am planning to move it from my server at home to another external (paid) webhost to be faster and more reliable.

    Can anybody provide instructions how to transfer(duplicate) my database to another server?

    Thank you.. I (and all other Tiki newbies around the world) will really appreciate it! 😀

    Reads: 2023
    Posted by Philippe Cloutier posts: 1001 Canada

    I don't remember a place where you can directly find this information.
    After transferring the database, there are a few things that are stored as files, like dumps, sometimes images and files. Then the only thing left to do will be to launch tiki-install.php with the new DB access info.


    Posted by Damian Parker posts: 2881 United Kingdom

    Hi!

    This is quite easy to do:

    1) Dump the database, using something like phpMyAdmin to a SQL file
    2) Delete all in your local copy of templates_c
    3) FTP your local tiki root to the hosts webspace
    4) If you dont have SSH access CHMOD the necessary directories and files using FTP otherwise SSH in and run ./setup.sh with the correct parameters
    5) Create your database by running the dumpd SQL file on your hosts db server
    6) edit the db/local.php file and enter your new database connection settings

    That should be everything!

    If you have trouble join us on the irc.freenode.net channel #tikiwiki


    Posted by Jonathan Smith posts: 26 United States

    I guess this is as good a place as any. Easy is in the eye of the beholder, Damian.

    On the MigratetoTiki page, either you missed my point or ignored it. The answers that you provide here and there are:
    1. DBMS dependent (MySQL centric)
    2. Version dependent (Tables change between versions)
    3. Tiki dependent (Now which attribute for which field for which table was that?)

    My grousing had to do with "Where is the Import/Export button?" Movable Type uses MySQL (or can use Berkley dB). Nevertheless, transporting data from one MT installation to another is done with a handy-dandy, Import/Export button.

    MT exports data as an easy-to-edit text file. Granted it is Personal Publishing Software, i.e., a weblog rather than a Swiss Army knife for collaborative content. Still, I would contend that transporting data is much simpler, "I push a button", instead of finding and following the steps presented, augmented, and outdated in this specific post.

    The (stupid user) defence rests. 🙄

    Posted by Damian Parker posts: 2881 United Kingdom


    I hear you! and it is a very valid point. Especially if you have mysql locally and say MSSQL on a host.

    I believe we have confirmd that the current Backup/Restore in TikiWiki isnt working. Lets add it to the list of things to get fixed in 1.8 before that goes Final!

    -Damian


    > jcwinnie:
    > I guess this is as good a place as any. Easy is in the eye of the beholder, Damian.
    >
    > On the MigratetoTiki page, either you missed my point or ignored it. The answers that you provide here and there are:
    > 1. DBMS dependent (MySQL centric)
    > 2. Version dependent (Tables change between versions)
    > 3. Tiki dependent (Now which attribute for which field for which table was that?)
    >
    > My grousing had to do with "Where is the Import/Export button?" Movable Type uses MySQL (or can use Berkley dB). Nevertheless, transporting data from one MT installation to another is done with a handy-dandy, Import/Export button.
    >
    > MT exports data as an easy-to-edit text file. Granted it is Personal Publishing Software, i.e., a weblog rather than a Swiss Army knife for collaborative content. Still, I would contend that transporting data is much simpler, "I push a button", instead of finding and following the steps presented, augmented, and outdated in this specific post.
    >
    > The (stupid user) defence rests. 🙄


    Posted by Damian Parker posts: 2881 United Kingdom


    I hear you! and it is a very valid point. Especially if you have mysql locally and say MSSQL on a host.

    I believe we have confirmd that the current Backup/Restore in TikiWiki isnt working. Lets add it to the list of things to get fixed in 1.8 before that goes Final!

    -Damian


    > jcwinnie:
    > I guess this is as good a place as any. Easy is in the eye of the beholder, Damian.
    >
    > On the MigratetoTiki page, either you missed my point or ignored it. The answers that you provide here and there are:
    > 1. DBMS dependent (MySQL centric)
    > 2. Version dependent (Tables change between versions)
    > 3. Tiki dependent (Now which attribute for which field for which table was that?)
    >
    > My grousing had to do with "Where is the Import/Export button?" Movable Type uses MySQL (or can use Berkley dB). Nevertheless, transporting data from one MT installation to another is done with a handy-dandy, Import/Export button.
    >
    > MT exports data as an easy-to-edit text file. Granted it is Personal Publishing Software, i.e., a weblog rather than a Swiss Army knife for collaborative content. Still, I would contend that transporting data is much simpler, "I push a button", instead of finding and following the steps presented, augmented, and outdated in this specific post.
    >
    > The (stupid user) defence rests. 🙄