Hi
Having tried and given up on both the VM, and apt-get on a fresh Debian system, I gave up on those methods.
But by hacking my way trough the described
Installing from Source procedure I managed to get a system running. I was only making a test setup so I did not document my actions much, so I base the following on my .bash_history
1: sudo apt-get install ruby2.3 zlib1g-dev build-essential imagemagick ruby-rmagick libmagickcore-dev libmagickwand-dev nodejs libruby2.3 libsqlite3-dev libmariadbclient-dev libmariadbclient18 git-core libxslt-dev apt-transport-https
2: sudo apt-get install apache2-mpm-worker libcurl4-openssl-dev libssl-dev zlib1g-dev apache2-prefork-dev libapr1-dev libaprutil1-dev
sudo apt-get install libcurl4-openssl-dev libssl-dev zlib1g-dev apache2-dev libapr1-dev libaprutil1-dev
sudo apt-get install mariadb
At some point I also did install som other stuff (not directly related to concerto I think)
sudo apt-get install -y curl gnupg build-essential
sudo apt-get install openssl
sudo apt-get install mycli
sudo apt-get install ruby-dev
Step 3.
I then made a user for concerto, created a directory at /var/www/concerto chown to concerto.
Change to user concerto and cd into the new dir and do something like
git clone https://github.com/concerto/concerto.git code
skip 5.
Instead edit config/database.yml to suit your database setup. In my case I replaced it with database.yml.mysql and edited the production section to fit a new empty database in mariadb
step 6. I took a detour around
Installing Passenger + Apache to insure that I had a working passenger running on Apache
In step 7. locate the systemd scripts and copy those to to systemd
sudo cp script/concerto-clock.service script/concerto-worker.service /etc/systemd/system/
Adjust WorkingDirectory, User and Group in both files
Disclaimer: The above is extracted from a lot of trial and error, so I very likely may have forgotten some actions
--
Klaus