Answers.Body: <p>Buildkit is not <em>designed</em> for production use but I can't think of any reason it <em>can't</em> be used that way. As your second question suggests, the upgrade procedure will indeed be different. Steps for upgrading on a buildkit install would be:</p>
  
  <ol>
  <li>Backup your database</li>
  <li>Do a <code>git checkout tagname &amp;&amp; git pull</code> for all 3 git repos (civicrm-core, civicrm-packages &amp; civicrm-yourcms).</li>
  <li>Run <code>setup.sh</code> with the correct arguments to regenerate code and download dependencies.</li>
  <li>Run the upgrader (can do this from the command line as well)</li>
  </ol>
  
  <p>You'll probably want to create a little script to do this for you.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-28T00:24:22.547Z
Answers.LastActivityDate: 2016-05-28T00:24:22.547Z
Answers.UserDisplayName: Coleman
Body: <p>Background: I am recreating our CiviCRM installation on top of Drupal inside a Docker container. After a significant amount of research, I have decided to incorporate the best parts of <a href="https://github.com/djcf/civicrm-docker">civicrm-docker</a> and the official <a href="https://hub.docker.com/_/drupal/">Drupal</a> Docker container. However, before I progress too far down this road, some questions came up.</p>
  
  <p>Q1: Is it sensical to run a production site that has been built using civicrm-buildkit?</p>
  
  <p>Q2: What is the update procedure for a civicrm-buildkit build?</p>
  
  <p>Q3: Should Drush be used instead of civicrm-buildkit?</p>
  
  <p>Q4: (open ended) Does anyone have experience they would like to share?</p>
  
  <p>I will keep an eye on this thread, but if anyone would like to chat realtime, I can also be found in IRC.</p>
  
  <p>Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-23T14:23:43.183Z
Comments.Text: Re: drush vs civicrm-buildkit: under the hood, buildkit does use Drush for Drupal. Other hosting models could be Aegirproject.org, for example (for site/civi farms).
Comments.UserDisplayName: bgm
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-10T00:05:53.437Z
Comments.Text: Djcf here. Glad you found my work useful. Rebasing off of the official drupal container seems like an inherently good idea. How did you get on in the end? Would you care to share your docker build scripts?
Comments.UserDisplayName: DMCoding
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-11T16:15:56.890Z
Comments.Text: Yeap! It is on my [GitHub](https://github.com/altsalt/civicrm-docker), however, there are some local changes that I haven't pushed yet which fix a couple of serious bugs with the current version. Aka, don't try to run the update script.
Comments.UserDisplayName: Salt
Tags: <drupal><installation><best-practice><security><civicrm-buildkit>
Title: Is civicrm-buildkit safe to use in production?
ThreadText: # Is civicrm-buildkit safe to use in production?
  
  (Asked by: username_0 on 2016-03-23)
  
  Background: I am recreating our CiviCRM installation on top of Drupal inside a Docker container. After a significant amount of research, I have decided to incorporate the best parts of [civicrm-docker](https://github.com/djcf/civicrm-docker) and the official [Drupal](https://hub.docker.com/_/drupal/) Docker container. However, before I progress too far down this road, some questions came up.
  
  Q1: Is it sensical to run a production site that has been built using civicrm-buildkit?
  
  Q2: What is the update procedure for a civicrm-buildkit build?
  
  Q3: Should Drush be used instead of civicrm-buildkit?
  
  Q4: (open ended) Does anyone have experience they would like to share?
  
  I will keep an eye on this thread, but if anyone would like to chat realtime, I can also be found in IRC.
  
  Thanks!
  
  **Tags:** drupal, installation, best-practice, security, civicrm-buildkit
  
  > **Comments:**
  > **username_1**: Re: drush vs civicrm-buildkit: under the hood, buildkit does use Drush for Drupal. Other hosting models could be Aegirproject.org, for example (for site/civi farms).  
  > **username_2**: Djcf here. Glad you found my work useful. Rebasing off of the official drupal container seems like an inherently good idea. How did you get on in the end? Would you care to share your docker build scripts?  
  > **username_0**: Yeap! It is on my [GitHub](https://github.com/altsalt/civicrm-docker), however, there are some local changes that I haven't pushed yet which fix a couple of serious bugs with the current version. Aka, don't try to run the update script.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2016-05-28. Score: 2
  
  Buildkit is not *designed* for production use but I can't think of any reason it *can't* be used that way. As your second question suggests, the upgrade procedure will indeed be different. Steps for upgrading on a buildkit install would be:
  
  1. Backup your database
  2. Do a `git checkout tagname && git pull` for all 3 git repos (civicrm-core, civicrm-packages & civicrm-yourcms).
  3. Run `setup.sh` with the correct arguments to regenerate code and download dependencies.
  4. Run the upgrader (can do this from the command line as well)
  
  You'll probably want to create a little script to do this for you.
  
  
  ---
  
  