summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authoreinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2006-11-06 19:03:20 +0000
committereinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2006-11-06 19:03:20 +0000
commit0a0b21103237ba49f59cc5e35672a72fb9aee009 (patch)
treecc7b3f46369ff732ba181ec30a0b36df22e955ca /doc
parent75902072274845b909103bc6046e7c1b978c4dfe (diff)
Updated Readme and fixed stupid .htaccess suggestions
git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@487 4979c152-3d1c-0410-bac9-87ea11338e46
Diffstat (limited to 'doc')
-rwxr-xr-xdoc/README50
-rwxr-xr-xdoc/README.DB20
2 files changed, 15 insertions, 35 deletions
diff --git a/doc/README b/doc/README
index 64e5ee21..c3a1cb5d 100755
--- a/doc/README
+++ b/doc/README
@@ -51,7 +51,7 @@ Non specific, see requirements.
REQUIREMENTS:
-------------
-1 - Perl, 5+
+1 - Perl, 5.8+
2 - http server (Apache, NCSA, httpi, thttpd, ...)
3 - SQL Server (PostgreSQL 8.0+)
4 - DBD (DBD-Pg)
@@ -74,7 +74,7 @@ INSTALLATION
------------------------------
unpack the tar.gz file in /usr/local
- tar xzvf ledger-smb-2.6.x.tar.gz
+ tar xzvf ledger-smb-x.y.z.tar.gz
you should now have everything in /usr/local/ledger-smb
@@ -127,7 +127,7 @@ SET PERMISSION:
---------------
change directory to /usr/local/ledger-smb
-# chown -hR nobody:nogroup users templates css spool
+# chown -hR nobody:nogroup templates css spool
replace nobody:nogroup with the web server user and group.
Some systems use apache:apache, www, www-data, ...
@@ -148,19 +148,13 @@ You can control this with an .htaccess file
c) protect the users directory with an .htpasswd file
-AuthGroupFile /dev/null
-AuthName "Unauthorized"
-AuthType Basic
-AuthUserFile /home/host.domain/private_html/ledger-smb/users/.htpasswd
-require valid-user
+order allow,deny
+deny from all
d) protect the templates directory with an .htpasswd file
-AuthGroupFile /dev/null
-AuthName "Templates"
-AuthType Basic
-AuthUserFile /home/host.domain/private_html/ledger-smb/templates/.htpasswd
-require valid-user
+order allow,deny
+deny from all
e) set up your PostgreSQL database and the tables.
@@ -173,8 +167,7 @@ some other tools like pgadmin.
http://host.domain.com/private_html/ledger-smb/admin.pl
to create the tables.
-There is no password so just hit the Enter key or click
-on "Continue".
+TODO: Add bit about setting admin password
Select the "Database Administration" link
@@ -200,8 +193,6 @@ Go to the next step, "SET UP A USER"
PREPARE YOUR SQL DATABASE SERVER:
---------------------------------
- PostgreSQL:
- -----------
add one database user with create database privileges
to manage the datasets and tables for LedgerSMB
@@ -213,11 +204,6 @@ PREPARE YOUR SQL DATABASE SERVER:
if you use passwords to access postgres use this command
$ createuser -d -P ledger-smb
- Install PL/PGSQL in template1 if it has not been installed yet
-
- # su postgres
- $ createlang plpgsql template1
-
SET UP A DATABASE AND TABLES:
-----------------------------
@@ -227,6 +213,11 @@ http://localhost/ledger-smb/admin.pl
Select the "Database Administration" link,
enter the user you created in the previous step.
+If the database has been pre-created for you (by
+your hosting company, you must leave the superuser
+credentials blank. If you want to create the
+database, fill in the superuser name and password.
+
The "Create Dataset" link queries the server
for existing datasets and displays them in a
table. Enter a name for the new dataset (use
@@ -236,7 +227,7 @@ Chart of Accounts and click on Continue.
You cannot manage any other datasets from this
interface, only the datasets used by LedgerSMB
-POSTGRESQL: template1 is only used to query
+Template1 is only used to query
the server, none of the information stored
in template1 is manipulated in any way.
You can connect to any other database you
@@ -261,18 +252,7 @@ http://localhost/ledger-smb/login.pl
UPGRADING TO A NEWER VERSION:
-----------------------------
-1. load admin.pl and lock the system
-2. untar the new version over top
-3. check the doc directory for specific notes
-4. load admin.pl and unlock the system
-5. log in
-
-NOTE: datasets are upgraded when you log in for
-the first time. During the upgrade process the
-dataset is locked so nobody can do any work.
-If an error occurs the system will remain locked.
-Track down the error, fix it, load admin.pl,
-unlock the system and log in again.
+TODO: Add bit about upgrading to 1.2 here.
UPGRADING WITH setup.pl:
diff --git a/doc/README.DB2 b/doc/README.DB2
deleted file mode 100755
index e69de29b..00000000
--- a/doc/README.DB2
+++ /dev/null