Creating your own Siteconfig Repository
You will use your own siteconfig
git repository to capture essential information that defines your desired Nucleator Customers, Accounts and Cages. For your first use of Nucleator, we suggest you use a public siteconfig maintained in your github account. Once you’ve seen how Nucleator Cages and Stacksets work, you can set up a private siteconfig repository and provide Nucleator with a distribution key to access it.
Fork the nucleator-core-siteconfig into your own github account
- Log into github and navigate to https://github.com/47lining/nucleator-core-siteconfig
- Fork your own copy of this repository into your github account by clicking the "fork" button in the upper right
Update your Stackset sources to use your personal siteconfig
Insert the URL to your GitHub or other repository in this section of ~/.nucleator/sources.yml
:
# siteconfig - Nucleator customer- and cage- specific configuration - src: git+git://github.com/<your_github_account>/nucleator-core-siteconfig.git version: master name: siteconfig
You will want to put in a link similar to "git+git://github.com/Java1Guy/nucleator-core-siteconfig.git" for a public GitHub repository.
Advanced: Using a siteconfig in a private repository
For your first use of Nucleator, this quickstart recommends that you use a public siteconfig. Once you’ve seen how Nucleator Cages and Stacksets work, you can create a private siteconfig repository and provide Nucleator with a distribution key to access it.
Note the clone URL for your personal siteconfig repository
Create a local clone:
cd <place_where_you_create_git_clones> git clone <clone_url_noted_above>
create access keys for the repository and place them in your ~/.ssh/distkeys directory.
Add a section to ~/.nucleator/distkeys.yml similar to this:
distkeys.yml# Customer Private GitHub Repository2 - hostname: github.com ssh_config_host: github-siteconfig private_keyfile: your.access.key.repo2.github.com.id_rsa
Next: Choosing Nucleator Stacksets