@@ -90,11 +111,18 @@ $ su
- Run make aspdocs
- Copy aspdocs/ to your web server's document space.
-
- Create a Global directory, such as /usr/local/etc/freeside/asp-global/
-
- Copy htetc/global.asa to the Global directory.
+
- Create a Global directory, such as /usr/local/etc/freeside/asp-global/:
+
+mkdir /usr/local/etc/freeside/asp-global/
+chown freeside /usr/local/etc/freeside/asp-global/
+
+ - Copy htetc/global.asa to the Global directory:
+
+cp htetc/global.asa /usr/local/etc/freeside/asp-global/global.asa
+
- Configure Apache for the Global directory and to execute .cgi files using Apache::ASP. For example:
-<Directory /usr/local/apache/htdocs/freeside-asp>
+<Directory /usr/local/apache/htdocs/freeside-asp>
<Files ~ (\.cgi)>
AddHandler perl-script .cgi
PerlHandler Apache::ASP
@@ -102,25 +130,25 @@ PerlHandler Apache::ASP
<Perl>
$MLDBM::RemoveTaint = 1;
</Perl>
-PerlSetVar Global /usr/local/etc/freeside/asp-global/
+PerlSetVar Global /usr/local/etc/freeside/asp-global/
+PerlSetVar Debug 2
</Directory>
|
- - NOTE: Mason support is still a bit buggy in the 1.4.0 prereleases. This will be fixed before 1.4.0. You have been warned.
- Run make masondocs
- Copy masondocs/ to your web server's document space.
- Copy htetc/handler.pl to your web server's configuration directory.
- Edit handler.pl and set an appropriate data_dir, such as /usr/local/etc/freeside/mason-data
- Configure Apache to use the handler.pl file and to execute .cgi files using HTML::Mason. For example:
-<Directory /usr/local/apache/htdocs/freeside-mason>
+<Directory /usr/local/apache/htdocs/freeside-mason>
<Files ~ (\.cgi)>
AddHandler perl-script .cgi
PerlHandler HTML::Mason
</Files>
<Perl>
-require "/usr/local/apache/conf/handler.pl";
+require "/usr/local/apache/conf/handler.pl";
</Perl>
</Directory>
@@ -138,16 +166,16 @@ AuthUserFile /usr/local/etc/freeside/htpasswd
require valid-user
</Directory>
- - Create one or more Freeside users (your internal sales/tech folks, not customer accounts). These users are setup using using Apache authentication; they're not UNIX user accounts. For example, using mod_auth (flat files):
+
- Create one or more Freeside users (your internal sales/tech folks, not customer accounts). These users are setup using using Apache authentication, not UNIX user accounts. For example, using mod_auth (flat files):
- First user:
$ su
-$ freeside-adduser -h /usr/local/etc/freeside/htpasswd -c /usr/local/etc/freeside/secrets username
+$ freeside-adduser -c -h /usr/local/etc/freeside/htpasswd username
- Additional users:
$ su
-$ freeside-adduser -h /usr/local/etc/freeside/htpasswd /usr/local/etc/freeside/secrets username
+$ freeside-adduser -h /usr/local/etc/freeside/htpasswd username
- (using other auth types, add each user to your Apache authentication yand then run: freeside-adduser /usr/local/etc/freeside/secrets username
+ (using other auth types, add each user to your Apache authentication and then run: freeside-adduser username
- As the freeside UNIX user, run bin/fs-setup username to create the database tables, passing the username of a Freeside user you created above:
$ su freeside
|