Answers.Body: <p>Take a look at Jake Chapman's <a href="https://github.com/imjakechapman/CraftCMS-Boilerplate" rel="nofollow">Craft CMS - Boilerplate</a> on GitHub. You simply copy or clone your Craft boilerplate for each new project, and then add a newly downloaded <code>craft/app/</code> folder (wich is already on the latest Craft version) with a new <code>license.key</code> file to it.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-12T18:34:37.077Z
Answers.LastActivityDate: 2014-08-12T18:42:11.360Z
Answers.LastEditDate: 2014-08-12T18:42:11.360Z
Answers.UserDisplayName: carlcs
Answers.Body: <p>Relevant link: <a href="http://buildwithcraft.com/help/license-enforcement">http://buildwithcraft.com/help/license-enforcement</a></p>
  
  <p>But the TLDR is that purchases are tied to your <code>craft/config/license.key</code> file and the purchase will follow that file wherever it goes.</p>
  
  <p>So as long as your replication script ignores that file, you'll get a fresh one tied to Craft Personal Edition the first time that Craft sees it's has an internet connection and you can make a new purchase.</p>
  
  <p>Additionally, and regardless of edition, Craft will tie the <code>license.key</code> file to a domain when it thinks it's being run on a "public" domain.  <a href="http://buildwithcraft.com/help/license-enforcement#how-do-we-determine-craft-is-running-on-a-public-domain">Here is how we determine what is public.</a></p>
  
  <p>Even if Craft gets that wrong (maybe you develop on public staging domaina.com, but the site will ultimately be on a public domainb.com) and Craft ties the <code>license.key</code> file to the staging domaina.com, the worst that will happen is that when you deploy the <code>license.key</code> file to domainb.com, you'll get a alert in the control panel saying something to the affect of:</p>
  
  <p>"This license.key file is already in use on domaina.com.  Would you like to transfer it to domainb.com?"</p>
  
  <p>None of the site's functionality will be affected.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-12T18:48:20.020Z
Answers.Text: so a .gitignore of craft/config/license.key is all I need. Cool!
Answers.UserDisplayName: Marion Newlevant
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-12T18:35:33.977Z
Answers.LastActivityDate: 2014-08-12T18:35:33.977Z
Answers.UserDisplayName: Brad Bell
Body: <p>I want to create a basic Craft installation that I can use as my starting point. I don't want to just start with the Craft download, because there is a lot of common setup I don't want to repeat every time.</p>
  
  <p>My problem is making sure I properly pay Pixel &amp; Tonic for a new license each time I need one.</p>
  
Tags: <install><license>
Title: How to replicate a Craft installation as a starting point
ThreadText: # How to replicate a Craft installation as a starting point
  
  (Asked by: username_0 on 2014-08-12)
  
  I want to create a basic Craft installation that I can use as my starting point. I don't want to just start with the Craft download, because there is a lot of common setup I don't want to repeat every time.
  
  My problem is making sure I properly pay Pixel & Tonic for a new license each time I need one.
  
  **Tags:** install, license
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2014-08-12. Score: 9 | Accepted answer
  
  Relevant link: <http://buildwithcraft.com/help/license-enforcement>
  
  But the TLDR is that purchases are tied to your `craft/config/license.key` file and the purchase will follow that file wherever it goes.
  
  So as long as your replication script ignores that file, you'll get a fresh one tied to Craft Personal Edition the first time that Craft sees it's has an internet connection and you can make a new purchase.
  
  Additionally, and regardless of edition, Craft will tie the `license.key` file to a domain when it thinks it's being run on a "public" domain. [Here is how we determine what is public.](http://buildwithcraft.com/help/license-enforcement#how-do-we-determine-craft-is-running-on-a-public-domain)
  
  Even if Craft gets that wrong (maybe you develop on public staging domaina.com, but the site will ultimately be on a public domainb.com) and Craft ties the `license.key` file to the staging domaina.com, the worst that will happen is that when you deploy the `license.key` file to domainb.com, you'll get a alert in the control panel saying something to the affect of:
  
  "This license.key file is already in use on domaina.com. Would you like to transfer it to domainb.com?"
  
  None of the site's functionality will be affected.
  
  > **Comments:**
  > **username_0**: so a .gitignore of craft/config/license.key is all I need. Cool!  
  
  ---
  
  ### Answer by username_1 on 2014-08-12. Score: 2
  
  Take a look at Jake Chapman's [Craft CMS - Boilerplate](https://github.com/imjakechapman/CraftCMS-Boilerplate) on GitHub. You simply copy or clone your Craft boilerplate for each new project, and then add a newly downloaded `craft/app/` folder (wich is already on the latest Craft version) with a new `license.key` file to it.
  
  
  ---
  
  