Re: [Health-dev] Current Vanilla Installation

[Luis Falcon]

Dear Gerald

El Tue, 4 Jun 2024 14:52:44 +0200
Gerald Wiese <wiese@gnuhealth.org> escribió:
> Hello,
> 
> 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.

> 
> - 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.
> 
> - 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 ;)

> 
> - 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
> 
> - Client installation is missing " source $HOME/.bashrc" after
> putting something into it
> 
> (- Some strange symbols "&nbsp")

&nbsp is html for non-breaking space. Where did you see that one?


> 
> If desired I can fix some minor of those and open issues for the rest.
>
Of course! Thank you, Gerald!
 
> However I would like this to be resolved before:
> 
> https://codeberg.org/gnuhealth/his/issues/10


Happy hacking
Luis