Re: [Health-dev] Current Vanilla Installation

[Gerald Wiese]

Hello,

yes, we all agree libreoffice-nogui is Debian specific 😂 But it's 
missing there and was only present for Ubuntu.


About systemd paths:

/usr/lib/systemd/system: System units installed by the distribution 
package manager

/etc/systemd/system: System units created by the administrator

https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#

That's why I was putting it into /etc/ for Debian 12, openSUSE Leap 15.5 
& Ubuntu 22.04 - not only Ubuntu 18.04.

Seems like it's always appropriate if systemd is used and distribution 
package manager is not used.


I also think that nano would be a better choice. What I can tell from 
our courses is that students have way more problems with vi or vim, 
especially if they are new to console stuff. Vim might be more powerful 
but people don't even know how to start editing or exit which is just 
not beginner friendly.


Packages needed for client before pip installation should be the ones in 
"ghcl_packages" here:

https://codeberg.org/gnuhealth/ansible/src/branch/main/roles/gnuhealth-client/vars/main.yml


I guess I will:

- Resolve everything except uWSGI/Nginx in test branch and send it here 
before merging into main

- Continue working on the future vanilla installation

- See if people want to use something regarding uWSGI/Nginx from future 
vanilla already but don't change too much for now


Best

Gerald


On 05.06.24 10:11, Axel Braun wrote:
> Good morning,
>
> Am Dienstag, 4. Juni 2024, 15:13:21 MESZ schrieb Luis Falcon:
> > > I was looking a bit into the current vanilla installation and I see
> > > some problems:
> > >
> > > - Debian dependencies wget & libreoffice-nogui are missing
> > libreoffice-nogui does not ship in most OS, so we need to document it
> > on Debian specific instructions.
> libreoffice-nogui seems to be Debian-specific - could not find it in my 
> packages, or on OBS
>
> > > - This is one is needed several times and not properly documented
> > > when/where/how to use it:
> > >
> > > export PIP_BREAK_SYSTEM_PACKAGES=1
> > >
> > > (Needed for gnuhealth-setup as gnuhealth, gnuhealth-client as other
> > > user, potentially uwsgi as gnuhealth. .gnuhealthrc not automatically
> > > loaded, not clear how to "add this environment variable" for DAU
> > > either)
> > >
> > > - /etc/systemd/… is not only the proper path on Ubuntu 18.04, I think
> > > rather on most GNU/Linux
> > We should include the particular paths on each supported OS sections.
> /etc/systemd/.. for what (except systemd-configuration)? Sorry, cant spot it 
> from the text
>
> > > - No information how to install uWSGI
> > uWSGI is not part of gnuhealth-setup. We can include the
> > information from Thalamus setup:
> >
> > https://docs.gnuhealth.org//thalamus/#running-thalamus-from-a-wsgi-container
> >
> > > - No information how to install Nginx and where to put virtual host
> > > config
> > >
> > > - No information how to integrate uWSGI in systemd
> > We can include detailed information here:
> >
> > https://docs.gnuhealth.org/his/techguide/installation/vanilla.html#using-a-wsgi-server-for-gnu-health-hospital-management-component
> >
> > > - No information how to handle permissions Nginx <-> uWSGI socket
> >
> > > - "vi" as standard editor (e.g. after editconf) is not beginner
> > > friendly
> > Who said that? We all love vi and vim .
> >
> > We can always use ed ;)
> :-) nano someone?
>   
> > > - GTK client information is missing system requirements, e.g. on
> > > Debian:
> > >
> > > sudo apt install python3-gi python3-gi-cairo gir1.2-gtk-3.0
> > > libcairo2-dev libgirepository1.0-dev python3-dev
> The dependencies are unfortunately a little diferent between the different 
> Distributions....
>
> Cheers
> Axel