SQL-Ledger Homepage

SQL-Ledger User Forum

Forum index page

Log in | Register

Back to the board
Thread view  Mix view  Order
localguru(R)

E-mail

Germany,
18.03.2016, 02:40
 

Upgrade from 2.8.32 to 3.2.0 (General)

Hi,

I'm running sql-ledger since 7 years without any problems and rock solid. Thanks Dieter for sharing! My version is 2.8.32 (running on an old Debian) and I'd like to upgrade to the newest 3.2.0 on a current Ubuntu 14.04 LTS now.

Can I upgrade directly from 2.8.32 to 3.2.0 or with steps inbetween? Or should I setup a fresh 3.2.0 and try to import a sql-dump from my old 2.8.32 version?

Ciao
Marcus

Dieter Simader(R)

18.03.2016, 10:59

@ localguru

Upgrade from 2.8.32 to 3.2.0

Hi,

I'm running sql-ledger since 7 years without any problems and rock solid.
Thanks Dieter for sharing! My version is 2.8.32 (running on an old Debian)
and I'd like to upgrade to the newest 3.2.0 on a current Ubuntu 14.04 LTS
now.

Can I upgrade directly from 2.8.32 to 3.2.0 or with steps inbetween? Or
should I setup a fresh 3.2.0 and try to import a sql-dump from my old
2.8.32 version?

Ciao
Marcus

There is an UPGRADE file in the doc directory. download the source code and extract the file before you install over top.

There is no need to do a sql-dump, datasets are upgraded when you log in. However you must first edit the members file before you can log in.

After the upgrade to 3.2 populate the mimetype table (upgrade 3.0.8 -> 3.2)

localguru(R)

E-mail

Germany,
18.03.2016, 12:01

@ Dieter Simader

Upgrade from 2.8.32 to 3.2.0

Hi Dieter,

There is an UPGRADE file in the doc directory. download the source code and
extract the file before you install over top.


I setup a fresh Ubuntu 14.04 LTS and migrated my old 2.8.32 successfully to this machine. So far so good.

The plan is to upgrade to 3.2.0 now:

The steps are downloading the source, unpack it over /usr/local/sql-leger and do the steps in the UPGRADE file, right?

In the upgrade file section "Version 2.8.30 to 3.0" is relevant for me, right? Some questions to the upgrade file:

1. edit the members file and add the name of the dataset
to every login so the logins are 'login@dataset'

is it the username in [] in the file ../sql-ledger/users/members, like [marcus] to [marcus@sql-ledger]? My database is called sql-ledger.

2. copy one of the users and change the login to 'admin@dataset'
and remove the password

okay, it's just copy and paste in the ../sql-ledger/users/members file, right?

3. create a directory with the same name as the dataset
in the spool and templates directory

okay, after that we have:

/usr/local/sql-ledger/templates/sql-ledger
/usr/local/sql-ledger/spool/sql-ledger

4. move the private templates to the dataset directory

Don't understand. In 2.8.32 my templates are located in

/usr/local/sql-ledger/templates/marcus

Should I move all files from /usr/local/sql-ledger/templates/marcus to /usr/local/sql-ledger/templates/sql-ledger ?

5. move the spoolfiles to the dataset directory

Okay, my /usr/local/sql-ledger/spool/ directory is empty ?

6. if there are customizations create a 'custom' directory
in bin/mozilla and move all the custom_ files without the
custom_ prefix to the directory.

Inside /usr/local/sql-ledger/bin/mozilla I modified

am.pl and rp.pl

no custum_xxx.pl files there? What to do here?

7. if there are any user specific customizations create a
directory for each user in the 'custom' directory and move
all the files without the login_ prefix to the directory.

No login_xxx files in my installation

8. copy the following template to your dataset directory

$ cd sql-ledger/templates

$ cp Default-payslip.tex dataset/payslip.tex
$ cp Default-barcode.tex dataset/barcode.tex

Okay understand that.

9. set up printers in System -> Workstations

Okay

Note: replace 'dataset' with the name of your dataset.

Okay


There is no need to do a sql-dump, datasets are upgraded when you log in.
However you must first edit the members file before you can log in.

Can I go directly to from 2.8.32 to 3.2.0 or do I first need to upgrade to 3.0.8 and from there to 3.2.0?

And do I first have to login to admin.pl or with my normal "marcus" user to login.pl? Or as admin with blank password to login.pl?


After the upgrade to 3.2 populate the mimetype table (upgrade 3.0.8 -> 3.2)

Don't understand that? Where to populate the mimetype table and what is it?


Thanks for your time,
Marcus

Dieter Simader(R)

18.03.2016, 12:55

@ localguru

Upgrade from 2.8.32 to 3.2.0

Hi Dieter,

There is an UPGRADE file in the doc directory. download the source code
and
extract the file before you install over top.


I setup a fresh Ubuntu 14.04 LTS and migrated my old 2.8.32 successfully to
this machine. So far so good.

The plan is to upgrade to 3.2.0 now:

The steps are downloading the source, unpack it over /usr/local/sql-leger
and do the steps in the UPGRADE file, right?

In the upgrade file section "Version 2.8.30 to 3.0" is relevant for me,
right? Some questions to the upgrade file:

1. edit the members file and add the name of the dataset
to every login so the logins are 'login@dataset'

is it the username in [] in the file ../sql-ledger/users/members, like
[marcus] to [marcus@sql-ledger]? My database is called sql-ledger.

yes


2. copy one of the users and change the login to 'admin@dataset'
and remove the password

okay, it's just copy and paste in the ../sql-ledger/users/members file,
right?

yes


3. create a directory with the same name as the dataset
in the spool and templates directory

okay, after that we have:

/usr/local/sql-ledger/templates/sql-ledger
/usr/local/sql-ledger/spool/sql-ledger

yes


4. move the private templates to the dataset directory

Don't understand. In 2.8.32 my templates are located in

/usr/local/sql-ledger/templates/marcus

Should I move all files from /usr/local/sql-ledger/templates/marcus to
/usr/local/sql-ledger/templates/sql-ledger ?

move everything from /usr/local/sql-ledger/marcus to /usr/local/sql-ledger/templates/sql-ledger


5. move the spoolfiles to the dataset directory

Okay, my /usr/local/sql-ledger/spool/ directory is empty ?

then there is nothing to do here


6. if there are customizations create a 'custom' directory
in bin/mozilla and move all the custom_ files without the
custom_ prefix to the directory.

Inside /usr/local/sql-ledger/bin/mozilla I modified

am.pl and rp.pl

no custum_xxx.pl files there? What to do here?

you should have created custom_ files instead of changing the original files, makes it easier to apply changes when you upgrade.


7. if there are any user specific customizations create a
directory for each user in the 'custom' directory and move
all the files without the login_ prefix to the directory.

No login_xxx files in my installation

that's another level of customizations, nothing to do here.


8. copy the following template to your dataset directory

$ cd sql-ledger/templates

$ cp Default-payslip.tex dataset/payslip.tex
$ cp Default-barcode.tex dataset/barcode.tex

Okay understand that.

9. set up printers in System -> Workstations

Okay

Note: replace 'dataset' with the name of your dataset.

Okay


There is no need to do a sql-dump, datasets are upgraded when you log
in.
However you must first edit the members file before you can log in.

Can I go directly to from 2.8.32 to 3.2.0 or do I first need to upgrade to
3.0.8 and from there to 3.2.0?

And do I first have to login to admin.pl or with my normal "marcus" user to
login.pl? Or as admin with blank password to login.pl?


After the upgrade to 3.2 populate the mimetype table (upgrade 3.0.8 ->
3.2)

Don't understand that? Where to populate the mimetype table and what is
it?

cd /usr/local/sql-ledger/sql
psql -U dbuser dataset < Mimetype.sql

localguru(R)

E-mail

Germany,
20.03.2016, 10:51

@ Dieter Simader

Upgrade from 2.8.32 to 3.2.0

Hi Dieter,

thanks for your time. The upgrade was fine. :)

I've not tested everything, but I have a problem with creating invoice pdf documents. With version 2.8.32 on the same host, pdf invoices were created without problems. With the original invoice.tex I don't have any problems on 3.2.0 too, but with my own customized invoice.tex. The pdf document is fully created and I can find it in /usr/local/sql-ledger/users/, but inside the browser I see a lot of debug and error messages and the pdf is not offered for download. I'm not a tex expert, but is there a way to ignore warnings and errors as long as the pdf is created and offer it for download or send it a email attachment?

I've uploaded the error file here: https://files.fm/u/29adz5gx

Ciao
Marcus

localguru(R)

E-mail

Germany,
20.03.2016, 11:19

@ localguru

Upgrade from 2.8.32 to 3.2.0

Hi Dieter,

thanks for your time. The upgrade was fine. :)

I've not tested everything, but I have a problem with creating invoice pdf
documents. With version 2.8.32 on the same host, pdf invoices were created
without problems. With the original invoice.tex I don't have any problems
on 3.2.0 too, but with my own customized invoice.tex. The pdf document is
fully created and I can find it in /usr/local/sql-ledger/users/, but inside
the browser I see a lot of debug and error messages and the pdf is not
offered for download. I'm not a tex expert, but is there a way to ignore
warnings and errors as long as the pdf is created and offer it for download
or send it a email attachment?

I've uploaded the error file here: https://files.fm/u/29adz5gx

Ah, found it. It was a \\ newline, which caused the error.

Ciao
Marcus

Back to the board
Thread view  Mix view  Order
964 Postings in 318 Threads, 322 registered users, 161 users online (0 registered, 161 guests)
SQL-Ledger User Forum | Admin contact
RSS-Feed
powered by my little forum