-Sub-menus and Apache 2.0
-Some versions of Apache 2.0 (2.0.44+) don't expand sub-menus and generate
-a 500 error at various points. This stems from workaround developed for
-earlier versions of Apache 2.0. It looks like this workaround must now be
-disabled. If you get an error or the sub-menus don't expand edit
-SL/Form.pm and comment lines 80-82.
-
- # for Apache 2 we escape strings twice
-# if (($ENV{SERVER_SOFTWARE} =~ /Apache\/2/) && !$beenthere) {
-# $str = $self->escape($str, 1);
-# }
-
-
-
-About installation
-The easiest is to use the setup.pl script as root.
-You don't need to know very much about your system, just login as root,
-run 'perl setup.pl' and follow the prompts.
-setup.pl does not check for missing software packages and it is your
-responsibility to make sure you have the required pieces
-installed either from source or from a package supplied with your distro.
-
-
Requirements are clearly indicated in the README file and on the
-download page.
-
-
-
IDENT Authentication failed for user "postgres"
-
-This error has everything to do with the way the distros set up
-access rights for postgres. They are way too restrictive and leave you
-wondering what to do next.
-
-Do yourself a favour and change authentication in pg_hba.conf to
-
-
-local all trust
-
-until you have figured what all this stuff in pg_hba.conf does.
-
-
NOBODY, I repeat, NOBODY, from the Internet will be able to
-connect to postgres. You can't even connect from the inside LAN, the only
-one who is allowed to connect are clients originating from localhost.
-
-
Read a bit about the different authentication settings and change
-them as you see fit.
-It is all described in detail in pg_hba.conf
-
-
If you can't find the file, there is a wonderful utility called find.
-Use it.
-
-# find /usr/local -type f -name 'pg_hba.conf'
-
-
-
-DBD-Pg for Mandrake 9.0
-Mandrake did not package a compiled DBD-Pg package again, so install DBD-Pg
-from the source package.
-Install perl-DBD-Pg-1.01-4mdk.i586.rpm from the 'contrib' area.
-(Mandrake / 9.0 / contrib / RPMS)
-
-LaTeX error
-If for some reason LaTeX produces an error message check for strange
-characters in your account description and parts description
-and use \usepackage[latin1]{inputenc} in the preamble.
-
-
-LaTeX templates
-If you don't want to edit tex code by hand,
-you could use Lyx, Abiword, or any WYSIWYG editor capable of exporting
-latex code.
-To do that you must change the tokens for parameters <% and %> to something
-like << and >>. % is the comment character in tex. There is also a
-pagebreak block which must be commented out.
-When you are done with the changes
-replace << and >> with <% and %> and uncomment the pagebreak block.
-
-LaTeX is difficult but it also offers a much superior interface to produce
-professionally looking forms in postscript and PDF format.
-Unfortunately with power comes some pain too.
-
-
-
W3M
-pass terminal=mozilla when you start w3m
-$ w3m -F http://localhost/sql-ledger/login.pl?terminal=mozilla
-
-To use without frames
-$ w3m http://localhost/sql-ledger/login.pl?terminal=lynx
-
-PDF option disappeared
-Edit sql-ledger.conf and set $latex = 1;
-
sql-ledger.conf is perl code, check if it compiles, if it does not
-the internal defaults are used which set $latex to 0, hence no PDF option.
-
-SQL-Ledger on Mac Os X 10.1.5
-Jaume Teixi put together
-
-installation instructions to run SL on a Mac.
-
The instructions are for 1.8.5 however they still apply to any of the
-newer versions.
-
-Installation on Windows (WIN32)
-
-- install Apache, perl,
-Postgres
-or Oracle, DBI and the appropriate DBD
-module
-
if you can't compile DBD-Pg here is a precompiled
-DBD-Pg module
- - download the latest version of SQL-Ledger
-
- extract the files to c:\apache\sql-ledger
-
- download
-sql-ledger-windows.tar.gz
-and extract the files to c:\apache\sql-ledger
-
the shebang line is changed to c:\perl\bin\perl and the symlinks
- are regular files
-
answer with 'Yes' to overwrite existing files.
- - edit c:\apache\conf\httpd.conf and add
-
-Alias /sql-ledger/ "C:/apache/sql-ledger/"
-<Directory "c:/apache/sql-ledger">
- AllowOverride All
- AddHandler cgi-script .pl
- Options +ExecCGI
- Order Allow,Deny
- Allow from All
-</Directory>
-
-<Directory "c:/apache/sql-ledger/users">
- Order Deny,Allow
- Deny from All
-</Directory>
-
-
- - start Apache
-
- start Postgres|Oracle
-
- connect to http://localhost/sql-ledger/admin.pl and setup users
-and datasets
-
- connect to http://localhost/sql-ledger/login.pl and login
-
-
-
-Installation on Windows /w cygwin
-
-
-What do I enter for the language
-If you use English, nothing, if you want to use a foreign language for
-the login screen and admin stuff enter the language code. All the
-language specific files are in the locale directory. The long form for
-the language is in the LANGUAGE file.
-
-Mandrake 9.0 permission denied error
-Mandrake says to add this to your commonhttpd.conf
-
-<Directory /usr/local/sql-ledger>
- AllowOverride All
- Options -MultiViews -Indexes -FollowSymLinks
- Order allow,deny
- Allow from all
-</Directory>
-
-The way apache starts is it:
-Blocks all access to the physical file system /
-Opens access to the physical file system /var/www/html
-Opens access to the physical file system /var/www/perl
-Opens access to the physical file system /var/www/cgi-bin
-Opens access to the physical file system /var/www/protected-cgi-bin
-Opens access to the physical file system /home/*/public_html
-Opens access to the physical file system /home/*/public_html/cgi-bin
-Opens access to the physical file system /var/www/icons
-Opens access to the physical file system /usr/share/doc
-
-Since you're trying to access files outside of those allowed paths, you
-have to specifically allow it. It's done this way because of some past
-exploits with the pathnames. Rather than trust that there will never be
-another bug within apache that will let you get somewhere you don't
-want, you set it up securely out of the box so that apache won't let
-itself go somewhere that you don't want it to.
-
-
-
-Incorrect Dataset version
-The dataset you are trying to use is not compatible with the version.
-When you upgrade datasets use the same database user in the "User"
-field as the one listed in the Database section for the user.
-
-
-Mandrake 8.2
-Mandrake did not include the package "perl-DBD-Pg-1.01-1mdk.i586.rpm"
-You can install the package from Mandrake 8.1
-
-
-printing to a printer
-Setup a printer in the "Printer" field in the users preferences.
-i.e lpr -Plaser
-and set $latex = 1 in sql-ledger.conf
-LaTeX must be installed for this to work.
-
-To send the document to the printer check the "Postscript" or "PDF" format,
-enter the number of copies and click on the "Print" button.
-
-
The printer field is available only when you edit the user's
-preferences with admin.pl.
-
-
Note: html format is for screen preview. Use your browser's
-print function.
-
-
-
beginning balances
-Add a GL Journal entry and enter the beginning balance for your accounts.
-Use your balance sheet. If you also want to add open invoices, add the invoices
-and make the appropriate adjustments. Your balance sheet includes these
-amounts!
-
-
-cost for parts and service
-the cost will be updated when you purchase goods and services. You can
-enter the cost manually. This is so you can have a cost on file without
-making a purchase.
-
-
-establish a beginning inventory
-add the parts with a purchase invoice. Use the real cost for the items
-not zero. If you use zero cost then the cost of goods will be zero when you
-sell the item.
-
-
-Assemblies
-Assemblies are manufactured goods assembled from parts, services and
-assemblies. Because you do not buy assemblies you 'stock assemblies' by
-adding assembled units to your inventory. The quantity for individual parts
-is reduced and the quantity for the assembly increased. To disassemble an
-assembly you simply return the parts to inventory by entering a negative
-quantity for the number of assemblies to stock.
-
-
-customizing SQL-Ledger
-The application interface
-consists of a global and private interface.
-
-
-DBD-Pg not installed
-
-Most modern distributions now package DBD-Pg. If it is
-not packaged follow this recipe to get it working.
-
-
- - check if you have the header files for PostgreSQL
-
$ find / -name 'libpq-fe.h'
-
if nothing shows up install the development package for PostgreSQL
- - download and untar DBD-Pg
-
- set the environment variables POSTGRES_LIB and POSTGRES_INCLUDE
-
- cd to DBD-Pg directory
-
as ordinary user
-
$ perl Makefile.PL
-
$ make
-
$ make test
-
if all went well su to root
-
# make install
- - remove DBD-Pg
-
-
-
-SuSE 8.1 installation
-
-- Install the following using YaST2:
-
-
- perl-DBD-Pg
-
- postgresql
-
- postgresql-contrib
-
- postgresql-devl
-
- postgresql-docs
-
- postgresql-libs
-
- postgresql-perl
-
- postgresql-server
-
- postgresql-test
-
-
- Setup directories and paths for PostgreSQL:
-
-
> sux - (change to root)
-
-
- If not done by the installation, setup disk directory for your db:
-
# mkdir /var/lib/pgsql/data
-
# chown postgres /var/lib/pgsql/data
-
-
- Initialize the database, and start it, as below:
-
Note that there are man pages for initdb and pg_ctl.
-
-
# touch /var/log/pgsql
-
# chown postgres:postgres /var/log/pgsql
-
# sux postgres
-
-
- Initialize postgres:
-
> /usr/bin/initdb -D /var/lib/pgsql/data
-
(creating ... Success...)
-
-
- Start the postgres daemon:
-
> /usr/bin/pg_ctl -D /var/lib/pgsql/data -l /var/log/pgsql start (start db)
-
(postmaster successfully started)
-
-
- Quick-test the server (still as user postgres):
-
-
- > psql -d template1
-
(Welcome ... \q to exit psql)
-
\q
-
-
- Try setting up another db user:
-
-
> createuser <db-user> (<db-user> should match an existing Linux user)
-
Shall the new user be allowed to create databases? (y/n) y
-
Shall the new user be allowed to create more new users? (y/n) n
-
-
Unless a problem with DBD::Pg (perl interface), postgres is ready to go.
-
-
- If a previous sql-ledger database needs to be installed,
-
do the following as postgres user. Steps for dumping the old db,
- and building the new follow:
-
-> sux postgres
-
> psql template1
-
=# CREATE DATABASE my_database; (create your database)
-
=# \q
-
> cd /var/lib/pgsql/backups (assuming your backups are here)
-
The next command should have been performed earlier from the
- previous installed version of postgres and your database:
-
> pg_dump -d my_database.sql.bak (from previous ver postgres)
-
> cp my_database.sql.bak my_database.sql
-
- Use vi to change all occurrances of 'current_date' to current_date
- in file my_database.sql .
-
The vi command for this is :g/'current_date'/s//current_date/g
-
> psql my_database < my_database.sql > my_database.log
-
- Check my_database.log for errors.
-
-
- Download setup.pl and run it as root while on line to the internet:
-
-
# mkdir /usr/local/sql-ledger
-
# cd /usr/local/sql-ledger
-
# ./setup.pl
-
- Enter i
-
- Enter httpd owner and group if different than displayed default.
-
(Download occurs and status is displayed...)
-
-
- Setup the new sql-ledger with database.
-
-
- Surf to http://my_computer/sql-ledger/admin.pl
-
- Click enter (no password needed).
-
->Database Administration
-
- Leave fields Host and Port enpty for local installations.
-
- Enter your database name in the "Connect to" field.
-
- Enter the database user you setup (postgres, sql-ledger, etc.)
-
- Enter a password, only if a password is assigned to the database.
-
- To update an existing sql-ledger database: ->Update Database
-
Should see: The following Datasets need to be updated.
-
->Continue
-
Do more admin. You will need to setup at least one login.
-
To exit: ->Database Admin
-
-
- See if it works:
-
-
- Surf to http://my_computer/sql-ledger/login.pl
-
- Enter the login name you just created. Main menu screen should appear.
-
-
-
-
-Redhat Installation
-
-
-- Install apache1.3.12-25.i386.rpm
-
- Install perl5.6.0-9.i386.rpm
-
- Install postgresql-7.0.2-17.i386.rpm
-
- Install postgresql-server-7.0.2-17.i386.rpm
-
- Install postgresql-devel-7.0.2-17.i386.rpm (POSTGRES_INCLUDE)
-
- tar xvzf DBI-1.14.tar.gz
-
- cd DBI-1.14
-
- perl Makefile.PL
-
- make
-
- make install
-
- cd ..
-
- tar xvzf DBD-Pg-0.95
-
- cd DBD-Pg-0.95
-
- export POSTGRES_LIB=/usr/lib/pgsql
-
- export POSTGRES_INCLUDE=/usr/include/pgsql
-
- perl Makefile.PL
-
- make
-
- make install
-
- install SQL-Ledger
-
-
-Some of the applications have newer versions however the installation
-instructions remain the same. Just substitute the old version with a newer
-version.
-
-
-
Debian Installation
-
-
-
-
-The long version was provided by Gordon Haverland.
-
-
-- You need to unpack the SQL-Ledger package (compressed tar archive)
- someplace. Unpacking it in
- /usr/local/www/sql-ledger.
- Remember where you have unpacked it.
- - SQL-Ledger requires that the PostgreSQL database be installed.
-This is a very full-featured database, and has many associated
-packages. SQL-Ledger requires version 7.0 or better. The name
-of the basic package on Debian is postgresql. To find if you
-already have postgresql installed, and if so what version, the
-following command should work:
- dpkg -l | grep -i 'ii postgresql '
- A typical response would be:
- ii postgresql 7.1.3-5 Object....[stuff deleted]
- Indicating, that version 7.1.3 is installed (the -5 is a
- Debian patch level). You can use dselect or apt-get to install
- postgresql if you need to. You can visit the Debian maintainer's
- page for much more information on related packages at
- http://people.debian.org/~elphick/postgresql/
- Older versions of Debian's PostgreSQL installation use a file
- called postmaster.init, while newer versions use a file called
- postmaster.conf, either residing in /etc/postgresql.
- - SQL-Ledger requires a HTTP server (or daemon) which is capable of
- handling CGI scripts. Apache is the one which is recommended,
- version 1.3 or better. Debian calls the base package apache.
- Debian has two alternative versions of Apache, one with mod-perl
- (apache-perl) support compiled in, and the other with SSL
- (secure sockets layer - apache-ssl) support. SQL-Ledger doesn't
- require mod-perl or SSL support, but works with either if
- you need it installed for other functions you have. Older versions
- of Debian Apache installations, spread the configuration of the
- server across 3 files (srm.conf, access.conf and httpd.conf).
- Newer versions have consolidated all of this to httpd.conf.
-
- SQL-Ledger uses the Data Base Interface perl module for communication
- with PostgreSQL. The CPAN (Comprehensive Perl Archive Network)
- name for this module is DBI. Debian calls this module
- libdbi-perl. You should probably deselect (or apt-get) the
- Debian version of this module to minimize upgrading headaches in
- the future.
-
- DBI requires the use of an implementation specific Data Base
- Driver. In our case, we need the PostgreSQL specific one.
- CPAN calls this module DBD::PG, Debian calls it libdbd-pg-perl.
- You should use dselect (or apt-get) to install it.
-
- One more layer of Perl - PostgreSQL support is needed. Debian
- calls this last package libpgperl. Use dselect or apt-get to
- install it. (You should be able to install all 5 packages at
- one time.)
-
- We need to allow your PostgreSQL database to accept queries
- in a network manner. To do this, we need to change the value
- of the TCPIP_SOCKET to 1. In newer
- PostgreSQL installs, this variable will be someplace in
- /etc/postgresql/postgreslq.conf (older installs will be
- postmaster.init, same directory. Note: you shouldn't have
- both files there.) Start up your favorite text editor, find
- the line with that variable on it, change the "no" to a "yes",
- and make sure the line isn't commented out (a "#" in front
- of it on the same line).
-
- PostgreSQL has a set of users and passwords independent of
- normal user logins. We need to set up a PostgreSQL user
- to "own" the SQL-Ledger data (choose a name that makes sense
- to you, it shouldn't be "root" or "postgres"). The (PostgreSQL)
- program for doing this is called "createuser". To make this
- SQL-Ledger owner user, we first need to "become" the PostgreSQL
- superuser (on Debian, this is "postgres"), and then we will
- run the createuser program. So, once we are logged in as root:
-
- # su postgres
- $ createuser -d sql-ledger
- ...
- $ exit
- #
-
- As shown above, we then typed "exit" after createuser was done,
- to stop being the "postgres" user. The "-d" switch (you called
- also use "--createdb") specifies that this user can create
- databases.
- - We need to adjust the configuration of the HTTP server Apache
- next. Older Apache installations (srm.conf, access.conf and
- httpd.conf) need changes in srm.conf and httpd.conf. Newer
- installations just need to edit /etc/apache/httpd.conf. First,
- we need to instruct the server that files that end in ".pl"
- are to be treated as "cgi-script"s (srm.conf if separate).
- AddHandler cgi-script .pl
- Second, we need to map our SQL-Ledger installation to be easy
- for users to find it (in srm.conf if separate).
- Alias /sql-ledger/ /usr/local/www/sql-ledger/
- The "/" at the end of sql-ledger in both strings is important!
- Next, we need to allow the server to execute files from those
- directories, include things and follow links. This information
- is in httpd.conf (old or new installations).
- <Directory /usr/local/www/sql-ledger>
- Options ExecCGI Includes FollowSymLinks
- </Directory>
- If we decided to put SQL-Ledger somewhere other than
- /usr/local/www/sql-ledger, we would use different paths above.
- - All the files in the "users" and "templates" subdirectories
- of /usr/local/www/sql-ledger need to be owned by "www-data".
- # cd /usr/local/www/sql-ledger
- # chown www-data:www-data users templates users/members
- You may get an "error" about users/members not existing. It
- is safe to ignore this error.
- - Restart the apache server.
- /etc/init.d/apache restart
- - From a browser, visit the URL
- http://localhost/sql-ledger/admin.pl
- - Login as the PostgreSQL user responsible for the SQL-Ledger
- database you set up. Create a database and create
- at least one user. (It's not a good idea to access your
- SQL-Ledger data as the "owner" of the data on a regular basis.)
-
- Visit
- http://localhost/sql-ledger/login.pl
- and login as the user you created
-
-
-
-
-login.pl has compilation error
-
-This could be because of a missing configuration file in the users directory
-
-check the permission for the users directory. The directory must be
-set writeable for the webserver. If your webserver runs under nobody.nogroup
-set it to
-
-drwxrwx--x 2 johndoe nogroup 1024 May 26 16:49 users
-
-or
-
-drwx--x--x 2 nobody nogroup 1024 May 26 16:49 users
-
-
-
-script not executing, shows in browser instead
-
-Add
-
-
- AddHandler cgi-script .pl
-
-
-in your httpd.conf file.
-
-
-unknown terminal!
-the frontend script couldn't figure out which browser you are using
-include the terminal variable on the URL
-
- http://localhost/sql-ledger/login.pl?terminal=lynx
-Valid terminal variables are lynx and mozilla
-
-
-
permission denied at filesystem level
-
-Check if your web server has write permission to write to the following
-files and directories:
-
- users/
- templates/
- users/members
-
- # chown nobody:nogroup users templates users/members
-
-
-
-permission denied to access tables
-The user you entered in the "Database section" must be a valid
-database user who has the rights to access the tables.
-
-If the tables are owned by 'john' and you enter 'mary' as the dba
-you might run into this problem if mary doesn't have the rights to
-access tables owned by john.
-
-
-
html and graphics files don't show up on screen
-
-Enable Includes and FollowSymlinks Options in your httpd.conf file
- <Directory /usr/local/sql-ledger>
- Options ExecCGI Includes FollowSymlinks
- </Directory>
-
-
-
-Can I use mySQL
-
-No. mySQL lacks certain features required by SQL-Ledger.
-
-
-switch display to a foreign language
-
-Load your preferences and select the language.
-
Language selection is in accordance to
-
-ISO 3166-1 standards.
-
-
-Text shows in English when I use a foreign language
-
-This is because the corresponding hash entry is missing.
-Add the missing text in the locale/cc/all or locale/cc/missing
-file and run 'perl locales.pl' to rebuild the individual files.
-
-
cc refers to the country code.
-
-
-switch to a foreign language for the login and admin screen
-
-Edit sql-ledger.conf and enter the code for the variable
-$language. If your language specific files are in 'locales/cc', enter 'cc'
-
-
-
-
-