So after removing fail2ban (the VM host takes care of this in my setup), I have been greeted with
/etc/cron.daily/logrotate:
logrotate_script: 2: logrotate_script: fail2ban-client: not found
error: error running non-shared postrotate script for /var/log/fail2ban.log of /var/log/fail2ban.log
run-parts: /etc/cron.daily/logrotate exited with return code 1
Manual removal of fail2ban from /etc/logrotate.d required.
I've been using Turnkey apps for about a month or so (VMs in a Proxmox installation) and it has been a whole new level of ease of deployment for me so far.
I used to configure all these things all by myself for years, so ~2-3 days of work (sometimes even a week) to install, bughunt, configure and tweak a service such as trac or OTRS and similar.
I'm very new to Turnkey LAMP and Linux and I got disappointed at first glance because my Wordpress couldn't start - it brings 500 error. So I needed to dig into Apache log files where I found that I needed to activate some PHP modules. That's so so fine, probably because of security, but what pissed me of is that I needed to install curl by searching on internet and then logging into ssh in order to run such popular and generic web platform. I don't find this user friendly.
This is a thread to discuss the (ongoing) work of developing a new install method for the next (v15.2) release of the TurnKey GitLab appliance. It is a continuation of the discussion (inadvertently) kicked off by Royce by this comment. FWIW, there is also a related open feature request regarding this on our tracker.