===== Copy project to a remote host =====
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.
  - Copy Akelos to remote host.  This can take many hours.
  - Create databases on remote host.  To help with debugging, I am creating the development database and the production database.
  - Edit a copy of your project to fit the requirements of the new host.  (File names are from the project root.)
    - config/database.yml - Change the database specifications to match the remote host's requirements.
    - config/config.php
      - Change the AK_ENVIRONMENT definition from 'development' to 'production' if that's appropriate.
      - Change the AK_FRAMEWORK_DIR definition so that it points to your remote host's copy of Akelos.
      - Add the line <code php>define('AK_LOG_EVENTS', true);</code>It should go before the line<code php>include_once(dirname(__FILE__).DIRECTORY_SEPARATOR.'boot.php');</code>
  - Change the permissions on the copy of your project so that you can copy all of the files to the remote host.
  - Copy the files to the remote host.
  - Recreate the tables on the remote host.  
    - Locally, I used Webmin to back up my database to a sql file.  
    - On my remote host, I used phpMyAdmin to Import this file.
  - Run your project on the remote host 
  - Wonder why you get a blank screen.
    - Check the log files in the <project root>/log directory.  In my case, no log file was created.
    - It's time to check the forum... I found a post called [[http://forum.akelos.org/discussion/659/deploy-akelos/|Deploy Akelos]].  It has the same problem, but it hasn't been answered yet.FIXME

[[http://www.akelos.org/wiki/community-wiki#howtos|Return to HowTo page]]\\