1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
Debian Installation Notes for beancounter
On a Debian system, the following steps are required for beancounter to run:
0. In case you are upgrading from an older installation of beancounter,
run the script update_beancounter to add some columns to the tables.
1. Install PostgreSQL (if it is not yet installed)
root# apt-get install postgresql
which will also install postgresql-client and libpgsql2,
Configure postgresql with the defaults (ie SQL_ASCII) encoding and ISO
datestyle is my preference, others datestyles might or might not work.
2. Install all the other Perl packages required by beancounter:
root# apt-get install libdbd-pg-perl libdbi-perl
and the other packages.
3. Configure postgres to let the user as which you are running beancounter
create database etc:
root# su - postgres
postgres:~> createuser -d edd
Enter user's postgres ID or RETURN to use unix user ID: 1000 ->
Is user "edd" a superuser? (y/n) y
WARNING: Any user who can add users can also modify the system catalog
createuser: edd was successfully added
Note that the superuser rights might not be required, however it is
*important* to use the -d option to createuser.
4. Configure postgres to allow TCP/IP connections by uncommenting the
following line in /etc/postgresql/postmaster.init:
# PGALLOWTCPIP=no
PGALLOWTCPIP=yes
and restarting the postgresql daemon:
root# /etc/init.d/postgresql restart
5. Install beancounter
root# dpkg -i beancounter_0.1.0_all.deb
Selecting previously deselected package beancounter.
(Reading database ... 54112 files and directories currently installed.)
Unpacking beancounter (from beancounter_0.1.0_all.deb) ...
Setting up beancounter (0.1.0) ...
6. As the user running beancounter, run 'setup_beancounter' to initialise
the tables and run an example report.
7. That's it!
As of February 2001, I have yet to test it on a current Debian 'unstable'
release (with release-number-to-be 2.3 and codename 'woody'). There might be
issues with Postgresql 7.* that I am not yet aware of. If the reader of these
lines finds any, I would appreciate an email, preferably with some examples.
Update: There were some subtle changes from Postgresql 6.5.* to 7.* but it
works jus fine.
Update^2: We now also work with MySQL.
|
