Answers.Body: <p>I believe you're looking for the '<a href="http://buildwithcraft.com/docs/config-settings#allowAutoUpdates" rel="nofollow">allowAutoUpdates</a>' config option combined with <a href="http://buildwithcraft.com/docs/multi-environment-configs" rel="nofollow">multi-environment configs</a>.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-14T19:53:22.590Z
Answers.Text: FML - Sorry guys.
Answers.UserDisplayName: Jacob Graf
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-14T20:25:32.913Z
Answers.Text: It's all good, @JacobGraf :)
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-14T15:52:36.277Z
Answers.LastActivityDate: 2014-07-14T16:23:24.813Z
Answers.LastEditDate: 2014-07-14T16:23:24.813Z
Answers.UserDisplayName: Steve Abraham
Body: <p>In our workflow, we run a shared development server. Each developer develops locally but points to the development database. All Craft software updates need to happen while in the local environment and then changes need to immediately be committed to the git repo otherwise things could get really screwed up.</p>
  
  <p>I would the option to disable the update capability using a multi-environment config setting so we could prevent anyone from running those updates on the shared development server.</p>
  
  <p>I know we could set up user permissions to lock this down, but I think it would be much handier to be able to do that at the config level.</p>
  
  <p>Thoughts?</p>
  
Tags: <config><multi-environment><updating>
Title: Config option to disable update capability per environment
ThreadText: # Config option to disable update capability per environment
  
  (Asked by: username_0 on 2014-07-14)
  
  In our workflow, we run a shared development server. Each developer develops locally but points to the development database. All Craft software updates need to happen while in the local environment and then changes need to immediately be committed to the git repo otherwise things could get really screwed up.
  
  I would the option to disable the update capability using a multi-environment config setting so we could prevent anyone from running those updates on the shared development server.
  
  I know we could set up user permissions to lock this down, but I think it would be much handier to be able to do that at the config level.
  
  Thoughts?
  
  **Tags:** config, multi-environment, updating
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-07-14. Score: 5 | Accepted answer
  
  I believe you're looking for the '[allowAutoUpdates](http://buildwithcraft.com/docs/config-settings#allowAutoUpdates)' config option combined with [multi-environment configs](http://buildwithcraft.com/docs/multi-environment-configs).
  
  > **Comments:**
  > **username_0**: FML - Sorry guys.  
  > **username_2**: It's all good, @username_0 :)  
  
  ---
  
  