Server-Schulung-Teil9-Weiterer mit installieren von Kivitendo

From revampedia
Jump to: navigation, search

Preface

This training session took place on 05-11-17. We continued with the configuration of Kivitendo, but we didn't manage to finish it. We'll have to continue some other time and I have no idea how many more sessions will be necessary.

If there are still questions open after these instructions, please go to "Views" and then "Discussion" to leave your feedback, so I can add more Details to this page. jr


Change to Kivitendo directory and check it's status =

First we go back to the directory where we've installed Kivitendo

user1@vm1:~$ cd /var/www/git/kivitendo-erp/

And check it's status and in what branch we're currently in

user1@vm1:/var/www/git/kivitendo-erp$ git status
user1@vm1:/var/www/git/kivitendo-erp$ git branch


Install the latest version of Kivitendo

For that we need to switch to the master-branch

user1@vm1:/var/www/git/kivitendo-erp$ sudo git checkout master

And load the new packages with git

user1@vm1:/var/www/git/kivitendo-erp$ sudo git pull

New packages required by Kivitendo

During our training session we found out that the latest version requires additional packages. The script we've used before shows us what we're lacking:

user1@vm1:/var/www/git/kivitendo-erp$ ./scripts/installation_check.pl
Looking for File::MimeInfo::Magic ....................................... NOT ok
Looking for pdfinfo executable ................................... not installed

At the end it also gives us instructions on how to get them. We follow those instructions and install the available package

user1@vm1:/var/www/git/kivitendo-erp$ sudo apt install libfile-mimeinfo-perl

The second component wasn't found in cpan, so at the time I'm writing this that part isn't necessary.

Individual configuration for Kivitendo

If you're the administrator for several installations of Kivitendo it's absolutly necessary to customize some parameters. It doesn't hurt to have some individual settings if you just have one installation. For that we create a copy of the default configuration with a new name

user1@vm1:/var/www/git/kivitendo-erp$ sudo cp -a config/kivitendo.conf.default config/kivitendo.conf

And we edit the new file afterwards

user1@vm1:/var/www/git/kivitendo-erp$ sudo nano config/kivitendo.conf
admin_password = kivitendo123
cookie_name = kivitendo_session_id_vm1
user     = kivitendo
password = kivitendo
default_manager = swiss 

- admin_password is necessary when accessing Kivitendo in the browser.
- cookie_name should be individual for each installation of Kivitendo, as the administrator won't know in what installation he's currently working in.
- user and password are what we've set for the new user in PostgreSQL in Part8
- default_manager we set to Switzerland

That our changes become active we have to restart the service of the webserver

user1@vm1:/var/www/git/kivitendo-erp$ sudo systemctl restart apache2

Add a new user in PostgreSQL

This step is only necessary if you did Part8 before 05-15-17. If you do this at a later date have I made a correction to it.
First you change to the user postgres

user1@vm1:/var/www/git/kivitendo-erp$ sudo su postgres

And create the new user

postgres@vm1:/home/user1$ createuser -p 5433 -d -P kivitendo

-p 5433 -> tells us to what port we've connecting. As we've created a new cluster it's not the default port -d -> the new user is allowed to created databases -P -> We create a password for the new user

Access Kivitendo in the browser

In mz case I can access my installation of Kivitendo in the browser by entering the following address. It will be different for everyone

192.168.10.91:81

On the page we get we pick Administration. We have to enter the password that we entered in /var/www/git/kivitendo-erp/config/kivitendo.conf unter admin_password. In my case the password was kivitendo123.

The next page is already filled out and so we can klick "Datenbank anlegen" (create database).

Unfortunately we've run out of time and will have to continue at a later date.,