view release on metacpan or  search on metacpan

INSTALL.website  view on Meta::CPAN

(MySQL given just in case you need to change it back!)

*****NOTE*****

As of version 1.40 there is a more permanent way to do
this.

 - Create a file %%WEBSITE_DIR%%/conf/override_spops.ini

 - Open the file %%WEBSITE_DIR%%/conf/sample-override_spops.ini and
 copy the first 10 entries under 'REPLACE SPOPS DRIVER' and use the
 above table of database mappings to modify the relevant entries as
 directed.


(5) Install SQL files and data

If you'd like, go into the 'pkg/' directory and explore the files in
each package's 'data/' and 'struct' directories. These will be
executed in the next step, but if you'd like to change information go
ahead. 

Run the command:

 $ oi_manage --website_dir=%%WEBSITE_DIR%% \
             --package=INITIAL \
             install_sql

(Note: capitalization of 'INITIAL' is important!)

This installs the SQL structures and initial data for the packages
shipped with OpenInteract. Hopefully all the statements and programs
execute with an 'ok' status.

Be sure to view the status messages! Some packages might install
default information and give you details about that information in
these messages. 

For instance, the 'base_user' package creates a 'superuser' user
object and assigns it a random eight-character password. This password
is displayed in the status messages, and if you chose 'crypt_password'
in your configuration file you will NEVER be able to know the password
for the superuser. If this happens, you can just drop the database,
recreate it and re-run the 'install_sql' command.


(6) Change Directory Permissions

(NOTE: Win32 servers can skip this step, since the webserver usually
has sufficient permission for OpenInteract.)

To enable caching, browser editing/uploading of files you'll need to
modify the permissions on a few directories. The user who owns the
directories should be the same as the user your webserver runs as --
most of the time this is 'nobody'.

To do this, just run:

 $ cd %%WEBSITE_DIR%%
 $ chown -R nobody html/
 $ chown -R nobody cache/
 $ chown -R nobody overflow/
 $ chown -R nobody uploads/


(7) Edit Apache virtual host configuration

Using the static/modperl configuration assumes that you have already
setup a front-end proxy configuration as discussed at the following
URLs:

 http://perl.apache.org/guide/strategy.html#Alternative_architectures_for_ru
 http://perl.apache.org/guide/scenario.html#One_Light_and_One_Heavy_Server_w
 http://perl.apache.org/guide/scenario.html#mod_proxy

Further, OpenInteract assumes that if you're running the proxy server
configuration you've setup the front-end to pass the IP address to the
back-end, as described in:

 http://perl.apache.org/guide/scenario.html#Getting_the_Remote_Server_IP_in_

The OpenInteract Administrator's Guide (found in doc/admin.html) has
details about building the different servers. It's definitely worth
the time to read about this setup because it can help OpenInteract be
a big success for you.

Edit the files:

 %%WEBSITE_DIR%%/conf/httpd_static.conf
 %%WEBSITE_DIR%%/conf/httpd_modperl.conf

And follow the directions there.

If you want to run OpenInteract without a proxy server in front, just
edit the file:

 %%WEBSITE_DIR%%/conf/httpd_modperl_solo.conf

And only bring that in (see next step).

If you're not using virtual hosts, then copy the information within
the <VirtualHost></VirtualHost> tags into your main config file and
skip the next step.


(8) Edit Apache configuration

If you're using the proxy server setup:

  In your static httpd server configuration, add the line:

    Include %%WEBSITE_DIR%%/conf/httpd_static.conf

  and in your mod_perl httpd server configuration, add the line:

    Include %%WEBSITE_DIR%%/conf/httpd_modperl.conf

If you're using the solo mod_perl setup:

    Include %%WEBSITE_DIR%%/conf/httpd_modperl_solo.conf

(9) Run Apache!