Freeside:1.7:Documentation:InstallingUsingYaST - Revision history

Rsiddall: /* Status */ Updating the status to match reality.

2009-04-14T20:46:52Z

‎Status: Updating the status to match reality.

Rsiddall: The installer needs to check the freeside user on the billing server can connect to the client machine via SSH

2009-04-14T20:26:24Z

The installer needs to check the freeside user on the billing server can connect to the client machine via SSH

Rsiddall: /* Basic setup and Apache webserver */ Added note about proxy server.

2009-04-08T14:55:41Z

‎Basic setup and Apache webserver: Added note about proxy server.

Rsiddall: Notes on starting self-service

2009-01-18T17:58:43Z

Notes on starting self-service

Rsiddall: Added notes on installing self-service unders SLES

2009-01-18T17:20:29Z

Added notes on installing self-service unders SLES

Rsiddall: /* Troublesome RPMs */ Gave some examples of architecture differences.

2009-01-01T01:32:40Z

‎Troublesome RPMs: Gave some examples of architecture differences.

Rsiddall: Removed errata as the RPMs should now handle all those edits. Fixed up instructions for enabling mod_perl from the command line. Moved instructions for downloading RPMs to fix Perl dependency problems

2009-01-01T01:29:04Z

Removed errata as the RPMs should now handle all those edits. Fixed up instructions for enabling mod_perl from the command line. Moved instructions for downloading RPMs to fix Perl dependency problems

Rsiddall: /* Basic setup and Apache webserver */ Clarifying the web server setup

2008-12-31T19:33:40Z

‎Basic setup and Apache webserver: Clarifying the web server setup

Rsiddall: Should be http-server, not http_server

2008-12-31T19:29:04Z

Should be http-server, not http_server

Rsiddall: Replaced instructions for setting up Apache via the YaST GUI with a simple command line invocation.

2008-12-26T17:20:01Z

Replaced instructions for setting up Apache via the YaST GUI with a simple command line invocation.

@@ Line 15: / Line 15: @@
 ===Status===
-The YaST version of Freeside does not include Request Tracker at this time.  The self-service interface conflicts with the main server installation and has been temporarily removed from the repository.  The MySQL backend has not yet been tested.  Only the 1.7 branch has been tested.  The version and release of the YaST package is shown in the "Billing Main" page in Freeside.
+The YaST version of Freeside does not include Request Tracker at this time.  The self-service interface no longer conflicts with the main server installation, but has been temporarily moved to its own repository.  The MySQL backend has not yet been tested.  Only the 1.7 branch has been tested.  The version and release of the YaST package is shown in the "Billing Main" page in Freeside.
 =Installation=

@@ Line 228: / Line 228: @@
 </pre>
-This will install the core self-service Perl modules, the self-service CGI scripts, and an Apache configuration file that makes the self-service available at https://www.example.com/selfservice/selfservice.cgi.  If you wish to configure Apache differently, either edit the configuration file after installation or install freeside-selfservice-cgi to skip the configuration file installation.
+This will install the core self-service Perl modules, the self-service CGI scripts, and an Apache configuration file that makes the self-service available at https://www.example.com/selfservice/selfservice.cgi.  If you wish to configure Apache differently, either edit the configuration file after installation or install freeside-selfservice-cgi instead of freeside-selfservice to skip the configuration file installation.
 * Restart the Apache web server:
@@ Line 236: / Line 236: @@
 </pre>
-* On your billing server, check the value of SELFSERVICE_MACHINES in /etc/default/freeside or /etc/sysconfig/freeside and start the freeside service.  Look at the log file for the self-service daemon to ensure it's connecting correctly to the client.  (Note that RPM-based self-service installations have the client daemon the billing server connects to located at /usr/sbin/freeside-selfservice-clientd, not under /usr/local/sbin.  You may have to edit freeside-selfservice-server on your billing machine to match.)
+* On your billing server, check the value of SELFSERVICE_MACHINES in /etc/default/freeside or /etc/sysconfig/freeside, make sure the freeside user can SSH into each of the self-service machines, and start the freeside service.  Look at the log file for the self-service daemon to ensure it's connecting correctly to the client.  (Note that RPM-based self-service installations have the client daemon the billing server connects to located at /usr/sbin/freeside-selfservice-clientd, not under /usr/local/sbin.  You may have to edit freeside-selfservice-server on your billing machine to match.)
 = Troublesome RPMs =

← Older revision		Revision as of 14:55, 8 April 2009
Line 24:		Line 24:

	* SSH in as root.		* SSH in as root.
		+
		+	* If you are installing to a machine behind a proxy server, run <code>yast2</code> and select <code>Network Settings : Proxy</code> and enter the proxy details so that YaST can access external repositories. (You can also set the proxy settings from the command line using <code>yast2 proxy</code>.)

	* Run "yast2" and select "Software : Installation Source", or (faster) enter "yast2 inst_source", and make sure the SLES repo is present. If not click Add and add the URL of the repo.		* Run "yast2" and select "Software : Installation Source", or (faster) enter "yast2 inst_source", and make sure the SLES repo is present. If not click Add and add the URL of the repo.

@@ Line 233: / Line 233: @@
 service apache2 restart
 </pre>
 = Troublesome RPMs =

← Older revision		Revision as of 17:20, 18 January 2009
Line 187:		Line 187:

	* If there have been any schema changes, run <code><nowiki>/usr/bin/freeside-update</nowiki></code>.		* If there have been any schema changes, run <code><nowiki>/usr/bin/freeside-update</nowiki></code>.
		+
		+	= Installing the Self-Service Interface =
		+
		+	On a new SLES system, complete the steps up to and including the "zypper installation" above. (You can skip installing mod_perl and omit "perl" in the list of Apache modules to enable.)
		+
		+	(Installing the self-service interface on the same system as the Freeside billing server is not recommended for security reasons. However, it is possible to install self-service by following these instructions after completing the billing server installation.)
		+
		+	* Use zypper to add the Freeside Self-Service repo:
		+
		+	=== 1.7.3 Stable repository ===
		+
		+	i386 (32-bit):
		+	<pre>
		+	zypper service-add http://freeside.biz/~rsiddall/repo/sles/10/freeside-1.7/stable/self-service/i386
		+	</pre>
		+
		+	x86_64 (64-bit):
		+	<pre>
		+	zypper service-add http://freeside.biz/~rsiddall/repo/sles/10/freeside-1.7/stable/self-service/x86_64
		+	</pre>
		+
		+	=== 1_7_BRANCH testing repository ===
		+
		+	i386 (32-bit):
		+	<pre>
		+	zypper service-add http://freeside.biz/~rsiddall/repo/sles/10/freeside-1.7/testing/self-service/i386
		+	</pre>
		+
		+	x86_64 (64-bit):
		+	<pre>
		+	zypper service-add http://freeside.biz/~rsiddall/repo/sles/10/freeside-1.7/testing/self-service/x86_64
		+	</pre>
		+
		+	* Install Freeside Self-Service:
		+
		+	<pre>
		+	zypper install freeside-selfservice
		+	</pre>
		+
		+	This will install the core self-service Perl modules, the self-service CGI scripts, and an Apache configuration file that makes the self-service available at https://www.example.com/selfservice/selfservice.cgi. If you wish to configure Apache differently, either edit the configuration file after installation or install freeside-selfservice-cgi to skip the configuration file installation.
		+
		+	* Restart the Apache web server:
		+
		+	<pre>
		+	service apache2 restart
		+	</pre>

	= Troublesome RPMs =		= Troublesome RPMs =

@@ Line 190: / Line 190: @@
 = Troublesome RPMs =
-You may have trouble getting yast2/zypper to install the newer versions of RPMs from the Freeside repository since libzypp considers build architecture to be more important than software version.  This problem is more prevalent on i386 systems.
+You may have trouble getting yast2/zypper to install the newer versions of RPMs from the Freeside repository since libzypp considers build architecture to be more important than software version.  This problem is more prevalent on i386 systems where it's easy to build an i386 RPM for which SLES has an older, i586, version.  However, you may also see it where you build a noarch RPM to replace a SLES x86_64 RPM.
 If zypper refuses to install the newer version from the Freeside repository, the most likely problem is that libzypp prefers the architecture of the RPM on the SLES repository.  You can confirm this by running (for perl-MailTools):

@@ Line 32: / Line 32: @@
 <pre>
 yast2 http-server modules enable=ssl,perl
 </pre>
@@ Line 118: / Line 119: @@
 zypper service-add http://freeside.biz/~rsiddall/repo/sles/10/freeside-1.7/testing/x86_64
 </pre>
 * Install Freeside:
@@ Line 146: / Line 134: @@
 </pre>
-* Work down the final steps to bring up a Freeside installation:
+* Optionally, check for troublesome RPMs:
-<pre>
+You may wish to spot check the version of a couple of RPMs at this point to detect problems now before the final stages of installation fail.
-== Errata ==
+For each of <code><nowiki>perl-DBI</nowiki></code> and <code><nowiki>perl-MailTools</nowiki></code>, do the following.
 <pre>
-echo "unset TEXINPUTS" >> /etc/profile.local
+zypper search perl-MailTools
 </pre>
-and apply the same change to the current session:
+which should show the installed version, marked with an 'i' in the left column, as being the same as the one on the Freeside repository.  If the installed version came from the SLES repository, see the section on troublesome RPMs.
 <pre>
-unset TEXINPUTS
+su postgres -c 'createuser -P freeside'
 </pre>
-* Edit /etc/init.d/apache2 and insert a line "unset TEXINPUTS" immediately after the line beginning "export ${!APACHE_*}".  (If you run a daily cron job to execute freeside-daily, no further changes should be necessary for typeset invoices to work.)
+A failure in freeside-setup may indicate a problem with your Freeside repository.  See the section on troublesome RPMs.
 * Restart the web server
@@ Line 183: / Line 163: @@
 service apache2 restart
 </pre>
 = Finalizing the installation =
@@ Line 205: / Line 187: @@
 * If there have been any schema changes, run <code><nowiki>/usr/bin/freeside-update</nowiki></code>.

@@ Line 36: / Line 36: @@
 * Setup SSL.  SLES does not ship with a working SSL configuration for Apache2.  You'll need to configure a virtual host and configure SSL on that virtual host.  First, scp the server certificate and key to /etc/apache2/ssl.{crt,key}, and copy any certificate authority bundles supplied by your certificate provider.
 <pre>
@@ Line 42: / Line 44: @@
 vi freeside-ssl.conf # Uncomment and correct ServerName, ServerAdmin, and any SSL file locations
 </pre>
 == Zypper setup ==

@@ Line 25: / Line 25: @@
 * SSH in as root.
-* Run "yast2", select "Software : Installation Source" and make sure the SLES repo is present.  If not click Add and add the URL of the repo.
+* Run "yast2" and select "Software : Installation Source", or (faster) enter "yast2 inst_source", and make sure the SLES repo is present.  If not click Add and add the URL of the repo.
 * Also add an update source if you're using a separate repo for updates.
-* While still in YaST, select "Network Services : HTTP Server" and walk through the configuration wizard.  It will show SSL disabled.
+* At the command line enter:
-* Exit YaST and setup SSL.  SLES does not ship with a working SSL configuration for Apache2.  You'll need to configure a virtual host and configure SSL on that virtual host.  First, scp the server certificate and key to /etc/apache2/ssl.{crt,key}, and copy any certificate authority bundles supplied by your certificate provider.
+<pre>
 <pre>