In the past I checked the whole functionality for the cloning feature in Virtualmin and reported a few errors. It helped me to get a development environment identical to the parent, without having to do any functionality settings (except cleaning some “relics” from the parent). I just brought the application by copying it to the file system and loaded the dump into the database. Everything worked without issues. It is recommended to do a test first before but not on a production server.
Thanks, this is a production VM but this one VS is not.
The VM has only one other VS using PHP and it has been live for oinks. (so am aware of some of the issues moving a dev DB to a live server - just not one from “LimeServey” - and tbh I don’t really want to dig too deep in their code to unravel it - my PHP skills ended way back with v5 )
I am trying to take a cautious approach, but as always time is of essence - the client is claiming everything is working and only needs to transfer it to a live server and test email (now where have I heard that before? )
I have the domain and have tested email so far so good
It is really all about my discomfort with the LimeSurvey product and lack of experience with it over the years since I last looked at it.
Can’t you give the client enough access for them to do it themselves, its putting alot on you to work this all out unless they paying extra apart from hosting cost.
give a happy coder enough rope and they are just as likely to want to climb the ladder and shove others off.
I was more interested if there was anyone else out there actually using this option of Virtualmin or if it was originally added historically and was no longer used.
In the old days I think I would have managed a different development route and avoided PHP altogether.
still, it is a good idea - if only to save my time/stress
)
)