Making OpenVPMS easy to install for new users
Hi,
I've been working on a script to simplify installation and upgrades for new implementors. I'm targeting linux hosting at the moment, but will consider a Windows installer as time permits. I've made the first version available here.
If anybody has Debian or Ubuntu Trusty and some time to test this script for me, any feedback would be welcomed.
Cheers
Damien
Re: Making OpenVPMS easy to install for new users
I don't work with those platforms, so I can't test it out for you. I would point out however that we have had reports that LibreOffice is not 100% compatible with OpenOffice. As per http://www.openvpms.org/documentation/csh/1.9/topics/installing-openvpms... :
Fields may not merge correctly, and documents created in LibreOffice may look different when printed via OpenVPMS.
Re: Making OpenVPMS easy to install for new users
Damien - I am afraid that I do not currently have time to test/exercise this, but I had a quick look through the script. You might bear in mind that rather than running an in-house linux box, people might want to host on an Amazon EC2 instance. We are now running production on one EC2 instance with a second hosting the standby system. I hope to document this in the near future. A quick look through your script leads to the following comments:
## DO NOT use sudo apt-get install automysqlbackup ### see instead https://www.rosehosting.com/blog/how-to-install-and-configure-automysqlb... ## /etc/default/automysqlbackup AND /etc/automysqlbackup/automysqlbackup.conf ###### set CONFIG_mysql_dump_master_data=2 ## edit /etc/cron.daily/automysqlbackup to be: #!/bin/sh test -x /usr/local/bin/automysqlbackup || exit 0 nice -n10 /usr/local/bin/automysqlbackup #### above to decrease impact of backup on night staff operation ### /etc/crontab - sets when hourly/daily/weekly/monthly jobs run - standard setting is around 0630 I change to around 0300 - ie: to get the daily automysqlbackup run at 0300 # m h dom mon dow user command 17 * * * * root cd / && run-parts --report /etc/cron.hourly 00 3 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) 25 3 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) 35 3 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly ) ## locale to enLANG=en_AU.UTF-8 # install language pack: sudo apt-get install language-pack-en # sudo nano /etc/default/locale to set LANG=en_AU.UTF-8 # list time zones: timedatectl list-timezones # set time zone: sudo timedatectl set-timezone Asia/Hong_Kong (or whatever zone you want)Damien - the other hairy thing is the printer support. Even if you are going to run the linux box locally, you need drivers for the label printers, and perhaps the other printers. I had problems with our Dymo label printers ( need to manually install drivers, and then get the labels to print the correct way up), and our two FujiXerox printers (no linux support so cannot print directly). However the two Brother printers work OK (with the help of TP Link print servers).
If you are going to use a cloud hosted system then you need to have a VPN to connect the printers - and this is a whole new bag of worms.
I applaud the effort to provide a script for new users. However, I suspect that it will be of more use to linux competent/openvpms incompetent techos than vets trying to do an initial install.
Regards, Tim G
Re: Making OpenVPMS easy to install for new users
Tim A and Tim G,
Excellent feedback, thankyou. I have tweaked the installation script accordingly.
Tim G, a comment on label printers. Wrestling with these can be time consuming. Would it be worthwhile making a brand recommendation to newcomers in the OpenVPMS install notes? Dymo printers work well with drivers pre-packaged in linux distributions.
The Dymo driver installation can certainly be automated - I will add this option to the easy installer (as time permits).
Regarding VPNs for printing - I've found the VPN approach tedious to support. This was exacerbated with mobile vets using multiple devices to access OpenVPMS. With comprehensive encryption arriving (free TLS via LetsEncrypt and mandatory encryption in IPV6) I have deleted my VPNs.
Additionally, I found it simpler to use port forwarding to the printers at clinics. Every network printer I've used listens on port 515 for jobs. For security, the router can restrict printer ports into only accepting packets from the IP address of the OpenVPMS server.
A final comment on direct printing via OpenVPMS. I have found FujiXerox printers talk nicely with HP's Generic PCL 6 drivers. "apt-get install hpijs-ppds" does the trick. I haven't needed to seek other drivers for Brother and Fuji printers in many years.
Again, many thanks for your feedback
Damien