From 9951dac925264910d664b50d2fc33cf3dc1c734e Mon Sep 17 00:00:00 2001 From: ivan Date: Sun, 3 Dec 2000 13:45:15 +0000 Subject: patch from Jason Spence : admin.html doc, autocapgen --- htdocs/docs/admin.html | 53 ++++++++++++++++++++++++++++++++++++++++++++++++ htdocs/docs/config.html | 1 + htdocs/docs/index.html | 4 ++-- htdocs/docs/install.html | 1 + 4 files changed, 57 insertions(+), 2 deletions(-) (limited to 'htdocs/docs') diff --git a/htdocs/docs/admin.html b/htdocs/docs/admin.html index 8adddbe92..b6665e05e 100644 --- a/htdocs/docs/admin.html +++ b/htdocs/docs/admin.html @@ -4,3 +4,56 @@

Administration

Open up the root of the Freeside document tree in your web + browser. For example, if you created the Freeside document tree in + /home/httpd/html/freeside, and your web browser's DocumentRoot is + /home/httpd/html, open http://your_host/freeside/. Replace + "your_host" with the name or network address of your web server. + +
Once in the Freeside web interface, you must first create a + service. An example of a service would be a dial-up account or a + hosted virtual domain. + +
After you create your first service or services, you must then + create a package of that service or services which you will sell to + your customer. To allow flexibility in changing your service + offerings, Freeside requires that you bundle your services into a + package before customers may purchase them. For instance, you could + create a leased line package which would consist of a one-time + charge for the customer premise equipment, the monthly service fee + for the leased line, a backup dial-up account, and a support + contract. You could also create a leased line package which omits + the support contract simply by adding a new package that does not + include the support contract. + +
After you create your first package, then you must define who is + able to sell that package by creating an agent type. An example of + an agent type would be an internal sales representitive which sells + regular and promotional packages, as opposed to an external sales + representitive which would only sell regular packages of services. + +
After creating a new agent type, you must create an agent, and + assign the the agent type you just created to it. + +
If the service you created was of type svc_acct, you may have to + create a POP from the main menu before you can create your first new + customer. + +
If you are using Freeside to keep track of sales taxes, you must + define tax information for your locale by clicking on the "View/Edit + locales and tax rates" link on the Freeside main menu. + +
Finally, you may optionally set up a referral by clicking on the + "View/Edit referrals" link in the Freeside main menu. Referrals + will help you keep track of how effective your advertising is, by + helping you keep track of where customers heard of your service + offerings. You must create at least one referral. If you do not wish to + use the referral functionality, simply create a single referral only. + +
You should now be ready to sign up your first customer by + clicking on the "New Customer" link at the top of the Freeside main + menu. +

+ + diff --git a/htdocs/docs/config.html b/htdocs/docs/config.html index e42cfd8e1..db218d642 100644 --- a/htdocs/docs/config.html +++ b/htdocs/docs/config.html @@ -25,6 +25,7 @@ All further configuration files and directories are located in

apacheroot - The directory containing Apache virtual hosts

apachemachine - A machine with the apacheroot directory and user home directories. The existance of this file enables setup of virtual host directories, and, in conjunction with the `home' configuration file, symlinks into user home directories.

apachemachines - Your Apache machines, one per line. This enables export of `/etc/apache/vhosts.conf', which can be included in your Apache configuration via the Include directive. +

autocapnames - The presence of this file will cause Freeside to use Javascript in /htdocs/edit/cust_main.cgi to automatically capitalize the first and last names of customers.

bindprimary - Your BIND primary nameserver. This enables export of /var/named/named.conf and zone files into /var/named

bindsecondaries - Your BIND secondary nameservers, one per line. This enables export of /var/named/named.conf

bsdshellmachines - Your BSD flavored shell (and mail) machines, one per line. This enables export of `/etc/passwd' and `/etc/master.passwd'. diff --git a/htdocs/docs/index.html b/htdocs/docs/index.html index f5c43d02c..fa0459bca 100644 --- a/htdocs/docs/index.html +++ b/htdocs/docs/index.html @@ -12,10 +12,10 @@

Upgrading from 1.2.2 to 1.2.3

Upgrading from 1.2.3 to 1.2.4

Configuration files - +

Importing legacy data

File exporting and remote setup

fs_passwd diff --git a/htdocs/docs/install.html b/htdocs/docs/install.html index 300104b2d..21b575139 100644 --- a/htdocs/docs/install.html +++ b/htdocs/docs/install.html @@ -77,5 +77,6 @@ chmod 755 browse/*.cgi edit/*.cgi edit/process/*.cgi misc/*.cgi misc/process/*.c

Create the `/usr/local/etc/freeside/counters.datasrc', and `/usr/local/etc/freeside/export.datasrc' directories for each datasrc (owned by the freeside user).

As the freeside user, run bin/fs-setup to create the database tables. +

Now proceed to the initial administration of your installation. -- cgit v1.2.1