1
edit
Changes
→Approach
<!-- Describe the approach to the project -- method/procedure/tools etc -->
The approach all along for the project has been to streamline the MySQL and Apache configuration required for setting up Weave. Because of this certain functionality is not enabled in the config files, such as SSL and Captcha.
For the MySQL streamlining a script has been developed for inclusion in the package to automate the creation of a database, three tables, and service account required for Weave to function. You can download/view the script here: [http://matrix.senecac.on.ca/~jpmorgan/SCRIPTS/weave.sql].
The approach for the Apache config was to avoid touching the main httpd.conf file. To do this the package installs the weave.conf file in /etc/httpd/conf.d/ which the service will pick up after a successful restart. As SSL is not enabled in the packaged version the weave.conf consists only of Alias configuration and not SSL virtualhost.
= Challenges =