OneBlink CDN CLI

This tool is for deploying client side code for web apps to the OneBlink CDN.

Usage

See the CLI help the CDN Command by running the following:

oneblink cdn --help

Setting Scope

Before you deploy, you will need to set the scope for your project. The scope will specify where your project will be deployed to.

This is the domain you set when creating the CDN address within the OneBlink Console.

oneblink cdn scope customer-project.cdn.oneblink.io

Deploying files

Authentication

Before you’re able to deploy to a CDN Hosting Environment, you will need to be authenticated. This is done by logging in with the OneBlink Login Command. Please see: OneBlink Login for more information on how to log in.

Example

Running:

oneblink cdn deploy www

on a directory with the following:

|-- .blinkmrc.json
|-- www
|   |-- index.html
|   |-- js
|   |   |-- app.js
|   |-- img
|   |   |-- logo.png
|   |   |-- cta.jpg
|   |-- css
|   |   |-- layout.css
|   |   |-- bootstrap.css

will deploy the following folder structure on the CDN:

|-- index.html
|-- js
|   |-- app.js
|-- img
|   |-- logo.png
|   |-- cta.jpg
|-- css
|   |-- layout.css
|   |-- bootstrap.css

Removing files from the cdn

Remove the files from your local folder, then deploy using --prune:

oneblink cdn deploy <path-to-files> --env <environment> --cwd <path-to-project> --prune

Single-page Applications

SPA (Single-page application) require that all URL paths return the index.html file and a 200 HTTP status response code. This is not the default configuration for a CDN Hosting environment. However, it simple to turn on. In your .blinkmrc.json file, simply add an isSinglePageApplication with a value of true under the cdn property.

Example

{
  "cdn": {
    "scope": "customer-project.cdn.oneblink.io",
    "isSinglePageApplication": true,
  }
}

Security Response Headers

By default, a set of security headers will be present on all responses from the web server hosting your CDN project. These headers are:

{
  "Referrer-Policy": "strict-origin-when-cross-origin",
  "Strict-Transport-Security": "max-age=31536000",
  "X-Content-Type-Options": "nosniff",
  "X-Frame-Options": "SAMEORIGIN",
  "X-XSS-Protection": "1; mode=block"
}

These headers can be disabled by setting the disableSecurityResponseHeaders property to true in your .blinkmrc.json file, like so:

Example

{
  "cdn": {
    "scope": "customer-project.cdn.oneblink.io",
    "disableSecurityResponseHeaders": true,
  }
}

Web Application Firewall (WAF) protection

You can enable or disable WAF protection by setting the waf property for the applicable environment in your .blinkmrc.json file. If an environment is not specified in the .blinkmrc.json file, it will be defaulted depending on your other existing environments (if all enabled, then true, otherwise false).

Example

{
  "cdn": {
    "scope": "customer-project.cdn.oneblink.io",
    "waf": {
      "prod": true,
      "test": true
    },
  }
}