Answers.Body: <p>Right now, contacting support@buildwithcraft.com is the only way to retrieve a lost <code>license.key</code> file.</p>
  
  <p>In the future, once we add user accounts to buildwithcraft.com, we'll also be adding order and license management, so you'll be able to retrieve it from there as well.</p>
  
  <p>I've responded to your ticket with your proper <code>license.key</code> file.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-01-05T01:56:54.177Z
Answers.LastActivityDate: 2015-01-05T01:56:54.177Z
Answers.UserDisplayName: Brad Bell
Body: <p>I purchased a Craft Client license for a staging server we have, which uses Git for deployment.</p>
  
  <p>Unfortunately, I forgot to copy the license.key file to my local copy of the site before my last git push, and it got clobbered.</p>
  
  <p>Is there a way to retrieve my license? I have contacted Craft support, which I assume is the only way to get it back, however if there is a way to get it back on my own that would be helpful.</p>
  
Tags: <license>
Title: How to get my license.key after deleting it via Git
ThreadText: # How to get my license.key after deleting it via Git
  
  (Asked by: username_0 on 2015-01-05)
  
  I purchased a Craft Client license for a staging server we have, which uses Git for deployment.
  
  Unfortunately, I forgot to copy the license.key file to my local copy of the site before my last git push, and it got clobbered.
  
  Is there a way to retrieve my license? I have contacted Craft support, which I assume is the only way to get it back, however if there is a way to get it back on my own that would be helpful.
  
  **Tags:** license
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-01-05. Score: 3 | Accepted answer
  
  Right now, contacting support@buildwithcraft.com is the only way to retrieve a lost `license.key` file.
  
  In the future, once we add user accounts to buildwithcraft.com, we'll also be adding order and license management, so you'll be able to retrieve it from there as well.
  
  I've responded to your ticket with your proper `license.key` file.
  
  
  ---
  
  