Answers.Body: <p>You should have a look into <a href="https://craftcms.com/docs/3.x/project-config.html" rel="nofollow noreferrer">project config</a> if you haven't already.</p>
  <p>It allows you to sync just the structural changes of your development, staging and live sites, without affecting the content/users.</p>
  <p>This way you can still sync your production database to staging, but then you can just sync the structural changes back to production – no freezing necessary.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-11T11:34:41.710Z
Answers.Text: Ideally the changes on the staging version would be content as well as structural. For example, I need to create a new section and fill it with content before moving to the live environment.
Answers.UserDisplayName: Andrew
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-11T11:55:35.317Z
Answers.Text: That's understandable. The way I would manage it – and this may not work for you – is to develop the structure locally with dummy/test content, push it live with project config but have it hidden from the front end, then input the content, then launch the new section. The only other way I can recommend is exposing your content on the development site with element api, then using feed me to sync the content in, but that involves quite a lot of setting up depending on the complexity of your content.
Answers.UserDisplayName: dmatthams
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-11T11:58:08.940Z
Answers.Text: Might also be worth checking out this plugin: https://plugins.craftcms.com/migrationassistant I have not used it however
Answers.UserDisplayName: dmatthams
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-11T19:02:51.397Z
Answers.Text: I've marked this as the correct answer, although I appreciate part of it is a work-around. Hope that's OK
Answers.UserDisplayName: Andrew
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-12T08:05:17.150Z
Answers.Text: Hey, I don’t mind if you post your solution and mark that as the answer :)  I’m interested to hear how you solved this.
Answers.UserDisplayName: dmatthams
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-11T10:45:42.967Z
Answers.LastActivityDate: 2021-03-11T10:45:42.967Z
Answers.UserDisplayName: dmatthams
Body: <p>What is the best way to keep live and staging environments synced with member registrations?</p>
  <p>I can export/import the database from the live to staging environment to keep it in sync - and have a content freeze on the live version during development on the staging version.</p>
  <p>But the live website will continue to allow new member accounts to be created, meaning the staging environment will be out of sync.</p>
  
Tags: <database><multi-environment><member><staging>
Title: How to keep staging install synced with member registration
ThreadText: # How to keep staging install synced with member registration
  
  (Asked by: username_0 on 2021-03-11)
  
  What is the best way to keep live and staging environments synced with member registrations?
  
  I can export/import the database from the live to staging environment to keep it in sync - and have a content freeze on the live version during development on the staging version.
  
  But the live website will continue to allow new member accounts to be created, meaning the staging environment will be out of sync.
  
  **Tags:** database, multi-environment, member, staging
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-03-11. Score: 2 | Accepted answer
  
  You should have a look into [project config](https://craftcms.com/docs/3.x/project-config.html) if you haven't already.
  
  It allows you to sync just the structural changes of your development, staging and live sites, without affecting the content/users.
  
  This way you can still sync your production database to staging, but then you can just sync the structural changes back to production – no freezing necessary.
  
  > **Comments:**
  > **username_0**: Ideally the changes on the staging version would be content as well as structural. For example, I need to create a new section and fill it with content before moving to the live environment.  
  > **username_1**: That's understandable. The way I would manage it – and this may not work for you – is to develop the structure locally with dummy/test content, push it live with project config but have it hidden from the front end, then input the content, then launch the new section. The only other way I can recommend is exposing your content on the development site with element api, then using feed me to sync the content in, but that involves quite a lot of setting up depending on the complexity of your content.  
  > **username_1**: Might also be worth checking out this plugin: https://plugins.craftcms.com/migrationassistant I have not used it however  
  > **username_0**: I've marked this as the correct answer, although I appreciate part of it is a work-around. Hope that's OK  
  > **username_1**: Hey, I don’t mind if you post your solution and mark that as the answer :)  I’m interested to hear how you solved this.  
  
  ---
  
  