- Beiträge: 5
- Dank erhalten: 1
Docker Image Feedback
we have been working on a production ready Docker Image for LimeSurvey and are looking for Feedback (issues, wanted features, tips for configuration, etc):
Using docker-compose the files in the repository will quickly startup a LimeSurvey instance.
Thanks and cheers,
Are you using a productive LimeSurvey setup with this docker image? With FPM?
visionit schrieb: are looking for Feedback (issues, wanted features, tips for configuration, etc):
I wonder why php-fpm cannot be used inside the docker image. Or is that design decision of yours?
What do you mean by "php-fpm cannot be used inside the docker image"?
$ docker run -ti --entrypoint php-fpm martialblog/limesurvey:fpm
[15-Aug-2018 07:10:01] NOTICE: fpm is running, pid 1
[15-Aug-2018 07:10:01] NOTICE: ready to handle connections
I was confused by this sentence.
But reading it now again I see additional web server and not additional container. So I got that wrong. Sorry for wasting your time.
To use the fpm image, you need an additional web server that can proxy http-request to the fpm-port of the container
Dockerising PHP application with nginx and php-fpm is common practice. This is usually a more flexible/scalable setup.
I did a search before starting another...
it is only missing data volumes. do you know if lime stores data in the www filesystem? or is it all db only?
will it be official/maintained?
how would the update process be? if we just replace the docker image with a new version and data volumes from the previous one, will limesurvey upgrade the data?
perhaps would be good to coordinate with the team.
What is the www-filesystem? Never heard that term, perhaps you mean the webrootpath as a storage destination?
412837 schrieb: it is only missing data volumes. do you know if lime stores data in the www filesystem? or is it all db only?
LimeSurvey stores data in files (e.g. config files, themes, uploads).
so all uploaded (persitent) user data is stored to the upload/ directory. Any other data (in www/) is application specific, thus getting changed when changing the version of the image. So what you want to do, is to use a Volume for /var/www/html/upload/
If you change the Image version you'll get the new LS version and the uploaded data stays the same.
I'd be very happy to get feedback for improvement from the LS Team.