createuser -D -I -R -S -P core_user
{code}

Create an empty database owned by that user:

{code

}
createdb -O core_user -T template0 core_test_db

{code}


{info}
Developer info: use this command to create an empty database with all definitions and transfer it directly to the dev host where the installer is:

*pg_dump -x --disable-dollar-quoting --attribute-inserts -O -s core | ssh cajones.org "cat - > /home/www/test.core.install/public/installer/sql/data.sql"*
{info}


h1. Change permissions

Change permission so that the following directories and files are writable by the webserver user:

{code=bash}
cd var/www/core/trunk
sudo chown -v www-data:www-data cache data/logs data/mails languages uploads public/includes
sudo chown -v www-data:www-data public/.htaccess public/index.php application/configs/application.ini
{code}


Must be populated with data:
* filetypes 
* roles
* timeslot_types

h2. Default conference & vhosts
THere should be at least one conference defined, with correct vhost, also in apache.

h2. File permissions
Make sure that appropriate directories are writable:




h2. default files
public/.htaccess-dist -> public/.htaccess
application/configs/application.ini-dist -> application/configs/application.ini


h2. files changes
.htaccess SETENV production ?
Default development, met message dat het daarna UITgezet moet worden.

In application.ini-dist the following need to be set: 

core.debugMailTo = "<email to send error reports to>"
core.observer.review = 1 (to toggle observer: review)

h2. Vacuum jobs using CRON

* mails
* orphan files


h2. Initial admin
Run the invitation code from the installer, asking for an email address which will become admin.