Skip to content
This repository was archived by the owner on May 23, 2019. It is now read-only.

Configuration Process for Internal Developers

Taylor Franklin edited this page Jun 7, 2016 · 12 revisions

In the public repo, you will notice that Bluepic-Server/cloud_config.json, Bluepic-Server/properties.json, and Bluepic-OpenWhisk/local.env are pretty empty. To populate those with the values we use for testing internally, follow these steps:

  1. Clone the Bluepic Testing Credentials repo:

    git clone https://github.com/IBM-Swift/BluePic-Testing-Credentials.git
    
  2. Next, clone the DevOps repo:

    git clone https://github.com/IBM-Swift/DevOps.git
    
  3. Now navigate to the /DevOps/scripts_assets/gradle_assets/build-deploy-assets/ directory, on your local machine, where the copy-project-properties.gradle script is.

  4. Make sure you have Gradle installed, if not, you can install it like this with Homebrew:

    brew install gradle
    
  5. Now, you simply run the script with the appropriate parameters. Here is an outline:

    gradle copyProperties -b copy-project-properties.gradle -PappOpenSourceFolder=<BluePic-Testing-Credentials-RootDirectory> -PappRootFolder=<BluepicRootDirectory>
    

    This script simply copies the files from -PappOpenSourceFolder and puts them in -PappRootFolder, overwriting if necessary and retaining the directory structure. Afterwards, the configuration files; Bluepic-Server/cloud_config.json, Bluepic-Server/properties.json, and Bluepic-OpenWhisk/local.env should be populated with valid credentials and will be untracked by git so we don't accidentally commit them to the remote repo.

Clone this wiki locally