Development

Stacklane doesn't require any special UI setup to start coding -- everything needed to run a Stacklane site is in standard file formats, hosted in a BitBucket or GitHub GIT repository. For ease of testing, we recommend using WebStorm and its Stacklane plugin.

Repositories

A repository URL is only needed for live deployment and testing from within the Stacklane management console UI. However we recommend creating and developing with a repository from the beginning. BitBucket and GitHub are supported GIT repository types.

Public

For public repositories, ensure that the repository is set to be publicly accessible. Then use the HTTPS GIT URL given in the BitBucket and GitHub UIs.

https://bitbucket.org/[group]/[repo].git
https://github.com/[group]/[repo].git

Private

For private repository deployment, Stacklane will be accessing a read-only version of your repository using SSH keys generated and securely hosted by Stacklane. When providing the GIT URL in the management console UI, use the SSH form given in the BitBucket and GitHub UIs.

git@bitbucket.org:[group]/[repo].git
git@github.com:[group]/[repo].git

Stacklane supports both a one-to-one and one-to-many model of SSH keys per repository. For the one-to-many model on GitHub you'll need to follow their "machine user" pattern.

IDE Plugins

WebStorm

+ Stacklane Plugin

WebStorm natively supports all Stacklane file formats, including GIT integration. Get the Stacklane plugin for WebStorm for easy testing.

Credentials

For certain functionality such as connectors to third party APIs, you'll need to define credentials with your build. Defining credentials is done with a JSON file that is specified in an IDE-specific way.

Basic Format


{
  "🔑":{
    "CREDENTIAL_NAME":{
      "KEY_NAME":"KEY_VALUE"
    }
  }
}
    

Example


{
  "🔑":{
    "api:site24x7.com":{
      "token":"[your-api-token]"
    }
  }
}