- Posts: 133
- Thank you received: 6
Welcome to the LimeSurvey Community Forum
Ask the community, share ideas, and connect with other LimeSurvey users!
Maintaining a dev environment for LimeSurvey
- mascarpone
- Topic Author
- Offline
- Premium Member
Less
More
9 years 3 weeks ago #117636
by mascarpone
Maintaining a dev environment for LimeSurvey was created by mascarpone
Hi All!
We are getting pretty heavy on LS and the idea of setting up a dev environment to test upcoming releases (and plugins, etc.) is sorts of forcing itslef to us... :whistle:
Question is: as anybody here worked on facilitating the replication of prod data towards the dev data so as to keep it as close as the prod as possible?
Cheers!
We are getting pretty heavy on LS and the idea of setting up a dev environment to test upcoming releases (and plugins, etc.) is sorts of forcing itslef to us... :whistle:
Question is: as anybody here worked on facilitating the replication of prod data towards the dev data so as to keep it as close as the prod as possible?
Cheers!
The topic has been locked.
- DenisChenu
- Offline
- LimeSurvey Community Team
Less
More
- Posts: 13910
- Thank you received: 2548
9 years 3 weeks ago #117644
by DenisChenu
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
I don't answer to private message.
Replied by DenisChenu on topic Maintaining a dev environment for LimeSurvey
Never do this, but a cron to
- Remove dev DB
- Copy prod db to dev db
Can be done.
Dev system update dev db if needed.
Denis
- Remove dev DB
- Copy prod db to dev db
Can be done.
Dev system update dev db if needed.
Denis
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
I don't answer to private message.
The following user(s) said Thank You: mascarpone
The topic has been locked.
- mascarpone
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 133
- Thank you received: 6
9 years 3 weeks ago #117685
by mascarpone
Replied by mascarpone on topic Maintaining a dev environment for LimeSurvey
Hi Denis,
Thanks for the prompt reply: I'm not sure what you're suggestion is though:
To simply overwrite the dev DB with prod DB to update it?
Or NOT to do that?
Cheers!
Thanks for the prompt reply: I'm not sure what you're suggestion is though:
To simply overwrite the dev DB with prod DB to update it?
Or NOT to do that?
Cheers!
The topic has been locked.
- DenisChenu
- Offline
- LimeSurvey Community Team
Less
More
- Posts: 13910
- Thank you received: 2548
9 years 3 weeks ago - 9 years 3 weeks ago #117688
by DenisChenu
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
I don't answer to private message.
Replied by DenisChenu on topic Maintaining a dev environment for LimeSurvey
No,
You can without any problem COPY the prod DB to the dev DB.
BUT : never use same DB for prod and dev : dev can update DB.
Denis
PS: i say : i never do this personnaly, but i'm sure it's OK.
You can without any problem COPY the prod DB to the dev DB.
BUT : never use same DB for prod and dev : dev can update DB.
Denis
PS: i say : i never do this personnaly, but i'm sure it's OK.
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
I don't answer to private message.
Last edit: 9 years 3 weeks ago by DenisChenu. Reason: add PS
The following user(s) said Thank You: mascarpone
The topic has been locked.
- mascarpone
- Topic Author
- Offline
- Premium Member
Less
More
- Posts: 133
- Thank you received: 6
9 years 3 weeks ago #117700
by mascarpone
Replied by mascarpone on topic Maintaining a dev environment for LimeSurvey
Ah ok I got it, definitely, yes!
When saying same, I meant an exact replication of the Prod DB - wouldn't have though it would be as easy as overwriting Dev with Prod occasionally - so good with me
Thanks for that
When saying same, I meant an exact replication of the Prod DB - wouldn't have though it would be as easy as overwriting Dev with Prod occasionally - so good with me
Thanks for that
The topic has been locked.
Moderators: Nickko