I try to automate the process of installation and updating LimeSurvey on our server.

As I'm used from other projects I try to use gitlab-runner and composer to install the software and add individual extensions (Plugins, themes, ...).

Usually we have a DEV-system, a TEST-system and the LIVE-system.
on DEV we develop additions or bugfix and save them to the extension repositories.
the Server is build and updated with composer and in the end is stored in the main repository

On TEST an image is build with a from the file.
Then data from the backup, which does not belong to the packages is copied (or linked) into the image, like individual DB-credentials, or files uploaded from admins (e.g. images).
In this way a copy of the former running installation should be generated (including all DB records and files not versioned in any package) which can be tested if no regression occured.

After verification the image can be copied to the LIVE-server, which has no read access to the net for security reason.

That is what we want to do with LimeSurvey too.
has anyone experiences with this or a similar deployment?

regarding the non-package data: which folders and files need to be copied or linked?

• Code:

  /application/config/config.php

  for the credentials
• Code:

  /plugins/*

  our project specific plugins
• Code:

  /upload

  or
  Code:

  /upload/survey

  ? for survey specific data uploaded from admins
• anything more?

LimeSurvey version ?

With 5.X : all is in ./upload for media file. And tmp is better out of any update (can be resetted each time)