Answers.Body: <p>You could use <a href="https://github.com/Pennebaker/craft-architect" rel="nofollow noreferrer">https://github.com/Pennebaker/craft-architect</a> to export your new sections/entry types/fields from your development environment once you're done, and then import them (without content) to production.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-30T23:01:00.747Z
Answers.Text: Great idea. I'll give this a shot. I'm also looking into content migrations as "the" potential solution to this issue, with the help of the "Migration Manager" plugin.
Answers.UserDisplayName: Cmagb
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-30T10:57:59.110Z
Answers.LastActivityDate: 2018-06-30T10:57:59.110Z
Answers.UserDisplayName: James Greig
Body: <p>What is the best practice for the following:</p>
  
  <p>Client site running CraftCMS (v3) is in production. Updates are needed which require additions or modifications to the data structure / schema of the site (new sections, fields, etc.). Taking a remote dump of the database for local development is not a realistic option as the client makes regular updates to the website in production. Particularly for new additions, is there a way to easily make those updates in production after I've completed them in my development environment?</p>
  
  <p>Real scenario: I'm adding a new section (a blog) to add to an existing Craft site. I will be working in the development environment for several days, making many additions to the data structure / schema, which I'd prefer not to have to replicate via the admin UI in production once I'm ready to deploy.</p>
  
  <p><em>Note: I do <strong>not</strong> want to sync the entire databases - just the structure.</em></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-30T06:09:44.473Z
Comments.Text: Would it be too much work to insert your fields, sections, entrytypes, fieldlayouts and fieldlayoutsfields table to the other database? If you need it more often you could also create a plugin that exports and imports those values via json
Comments.UserDisplayName: Robin Schambach
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-30T23:00:23.650Z
Comments.Text: @RobinSchambach great, in theory, but yes more work than seems reasonable. I am looking into the content migrations concept from yii as a potential solution, utilizing the "Migration Manager" plugin to make things a bit easier, because I'm not about to write the migration scripts for all of this. Perhaps this is the solution I'm looking for?
Comments.UserDisplayName: Cmagb
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-30T23:04:19.547Z
Comments.Text: I wouldn't say it's much work to check 6 select boxes in your DB interface and click on export and import it to your other DB - and an additional step for the content table. A content migration concept by yii2 is much more work since it's only a framework
Comments.UserDisplayName: Robin Schambach
Tags: <database><structure>
Title: Managing sections and field updates between environments
ThreadText: # Managing sections and field updates between environments
  
  (Asked by: username_0 on 2018-06-30)
  
  What is the best practice for the following:
  
  Client site running CraftCMS (v3) is in production. Updates are needed which require additions or modifications to the data structure / schema of the site (new sections, fields, etc.). Taking a remote dump of the database for local development is not a realistic option as the client makes regular updates to the website in production. Particularly for new additions, is there a way to easily make those updates in production after I've completed them in my development environment?
  
  Real scenario: I'm adding a new section (a blog) to add to an existing Craft site. I will be working in the development environment for several days, making many additions to the data structure / schema, which I'd prefer not to have to replicate via the admin UI in production once I'm ready to deploy.
  
  *Note: I do **not** want to sync the entire databases - just the structure.*
  
  **Tags:** database, structure
  
  > **Comments:**
  > **username_1**: Would it be too much work to insert your fields, sections, entrytypes, fieldlayouts and fieldlayoutsfields table to the other database? If you need it more often you could also create a plugin that exports and imports those values via json  
  > **username_0**: @username_1 great, in theory, but yes more work than seems reasonable. I am looking into the content migrations concept from yii as a potential solution, utilizing the "Migration Manager" plugin to make things a bit easier, because I'm not about to write the migration scripts for all of this. Perhaps this is the solution I'm looking for?  
  > **username_1**: I wouldn't say it's much work to check 6 select boxes in your DB interface and click on export and import it to your other DB - and an additional step for the content table. A content migration concept by yii2 is much more work since it's only a framework  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2018-06-30. Score: 1
  
  You could use <https://github.com/Pennebaker/craft-architect> to export your new sections/entry types/fields from your development environment once you're done, and then import them (without content) to production.
  
  > **Comments:**
  > **username_0**: Great idea. I'll give this a shot. I'm also looking into content migrations as "the" potential solution to this issue, with the help of the "Migration Manager" plugin.  
  
  ---
  
  