My personal preference is to make a copy of my Akelos project in another directory and do all my editing there. I then copy the files to the new host. This also provides me with a backup of what is on the host.

1. Copy Akelos to remote host. This can take many hours.
2. Create databases on remote host. To help with debugging, I am creating the development database and the production database.
3. Edit a copy of your project to fit the requirements of the new host. (File names are from the project root.)
   1. config/database.yml - Change the database specifications to match the remote host's requirements.
   2. config/config.php
      1. Change the AK_ENVIRONMENT definition from 'development' to 'production' if that's appropriate.
      2. Change the AK_FRAMEWORK_DIR definition so that it points to your remote host's copy of Akelos.
      3. Add the line

         define('AK_LOG_EVENTS', true);

         It should go before the line

         include_once(dirname(__FILE__).DIRECTORY_SEPARATOR.'boot.php');

4. Change the permissions on the copy of your project so that you can copy all of the files to the remote host.
5. Copy the files to the remote host.
6. Recreate the tables on the remote host.
   1. Locally, I used Webmin to back up my database to a sql file.
   2. On my remote host, I used phpMyAdmin to Import this file.
7. Run your project on the remote host
8. Wonder why you get a blank screen.
   1. Check the log files in the <project root>/log directory. In my case, no log file was created.
   2. It's time to check the forum… I found a post called Deploy Akelos. It has the same problem, but it hasn't been answered yet.

Return to HowTo page