New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

roku-deploy

Package Overview
Dependencies
Maintainers
1
Versions
86
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

roku-deploy

Package and publish a Roku application using Node.js

  • 0.2.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
6K
increased by45.81%
Maintainers
1
Weekly downloads
 
Created
Source

roku-deploy

Publish Roku projects to a Roku device by using Node.js.

Build Status Coverage Status NPM Version

Installation

npm install roku-deploy

Requirements

  1. Your project must be structured the way that Roku expects. The source files can be in a subdirectory (using the rootDir config option), but whever your roku files exist, they must align with the following folder structure:

    components/
    images/
    source/
    manifest

  2. You should create a rokudeploy.json file at the root of your project that contains all of the overrides to the default options. roku-deploy will auto-detect this file and use it when possible.

sample rokudeploy.json

{
    "host": "192.168.1.101",
    "password": "securePassword"
}

Usage

From a node script

var rokuDeploy = require('roku-deploy');

rokuDeploy({
    host: 'ip-of-roku',
    password: 'password for roku dev admin portal'
    //other options if necessary
}).then(function(){
    //it worked
}, function(){
    //it failed
});

From an npm script in package.json. (Requires rokudeploy.json to exist at the root level where this is being run)

{
    "scripts": {
        "deploy": "roku-deploy"
    }
}

Options

Here are the available options. The defaults are shown to the right of the option name, but all can be overridden:

  • host: string (required)
    The IP address or hostname of the target Roku device. Example: "192.168.1.21"

  • password: string (required)
    The password for logging in to the developer portal on the target Roku device

  • outDir?: string = "./out"
    A full path to the folder where the zip package should be placed

  • outFile?: string = "roku-deploy.zip"
    The name the zip file should be given.

  • rootDir?: string = './'
    The root path to the folder holding your project. The manifest file should be directly underneath this folder. Use this option when your roku project is in a subdirectory of where roku-deploy is installed.

  • files?: ( string | { src: string; dest: string; } ) [] =

    [
        "source/**/*.*",
        "components/**/*.*",
        "images/**/*.*",
        "manifest"
    ]
    

    An array of file paths, file globs, or {src:string;dest:string} objects that will be copied into the deployment package.

    Using the {src;dest} objects will allow you to move files into different destination paths in the deployment package. This would be useful for copying environment-specific configs into a common config location (i.e. copy from "ProjectRoot\configs\dev.config.json" to "roku-deploy.zip\config.json"). Here's a sample:

    {
         "src": "configs/dev.config.json",
         "dest": "app.config"
    }
    

    This will result in the [sourceFolder]/configs/dev.config.json file being copied to the zip file and named "app.config"

    NOTE: If you override this "files" property, you need to provide ALL config values, as your array will completely overwrite the default.

  • retainStagingFolder?: boolean = false
    Set this to true prevent the staging folder from being deleted after creating the package. This is helpful for troubleshooting why your package isn't being created the way you expected.

  • username?: string = "rokudev"
    The username for the roku box. This will always be 'rokudev', but allow to be passed in just in case roku adds support for custom usernames in the future

Click here to see the typescript interface for these options

FAQs

Package last updated on 26 Sep 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc