/Screenly-cli

Command Line Interface (CLI) and GitHub Actions workflow for Screenly.

Primary LanguageRustMIT LicenseMIT

Screenly Command Line Interface (CLI)

The purpose of Screenly's CLI is to make developer's life easier. Using our CLI, users are able to quickly interact with Screenly through their terminal. Moreover, this CLI is built such that it can be used for automating tasks.

Installation

Releases are built automatically. You can download the latest release here.

On macOS you can also use Homebrew to install the latest version.

$ brew tap screenly/screenly-cli
$ brew install screenly-cli

For other operating systems, you can either use the pre-compiled binaries, or use our Docker wrapper:

$ docker run --rm \
    -e API_TOKEN=YOUR_API_TOKEN \
    screenly/cli:latest \
    help
[...]

Usage

Assets

You can:

  • List your assets (list)
  • Get info on a particular asset (get)
  • Delete an asset (delete)
  • Inject JavaScript that runs when a web asset is rendered (inject-js)
  • Set custom HTTP heeaders when web assets are rendered (set-headers)
  • Helper function to set Basic Auth for authentication against web asset (basic-auth)

Examples

Add a web asset:

$ screenly asset add https://news.ycombinator.com "Hacker News"
+----------------------------+-------------+------+--------+
| Id                         | Title       | Type | Status |
+----------------------------+-------------+------+--------+
| XXXXXXXXXXXXXXXXXXXXXXXXX  | Hacker News | N/A  | none   |
+----------------------------+-------------+------+--------+

Upload a HTML file:

$ screenly asset add path/to/file.html "My File"
+----------------------------+-------------+------+--------+
| Id                         | Title       | Type | Status |
+----------------------------+-------------+------+--------+
| XXXXXXXXXXXXXXXXXXXXXXXXX  | My File     | N/A  | none   |
+----------------------------+-------------+------+--------+

This file will be served locally on your Screenly Player. You (currently) need to inline HTML/CSS/Images.

You can also use the --json feature, which is handy in conjuction with jq for getting say the Asset ID of a particular asset:

$ screenly asset list --json | \
    jq -r '.[] | select (.title|test("Hacker News")) | .id'
XXXXXXXXXXXXXXXXXXXXXXXXXX

Interact with screens

You can:

  • List your screens (list)
  • Get info on a particular screen (get)
  • Add/Pair a screen (add)
  • Revoke/delete (delete)

Examples

Listing screens:

$ screenly screen list
+----------------------------+-----------------------+-----------------------+---------+---------------------------------+-------------------+
| Id                         | Name                  | Hardware Version      | In Sync | Last Ping                       | Uptime            |
+----------------------------+-----------------------+-----------------------+---------+---------------------------------+-------------------+
| XXXXXXXXXXXXXXXXXXXXXXXXXX | Lobby Screen          | Screenly Player Max   |   ✅    | 2023-01-22T09:56:23.89686+00:00 | 8days 23h 18m 53s |
+----------------------------+-----------------------+-----------------------+---------+---------------------------------+-------------------+
| XXXXXXXXXXXXXXXXXXXXXXXXXX | Grafana Dashboard     | Raspberry Pi 3B+      |   ✅    | 2023-01-22T09:54:17.88319+00:00 | 10days 22h 9m 32s |
+----------------------------+-----------------------+-----------------------+---------+---------------------------------+-------------------+

Building

To build the Screenly CLI, you need to install Rust. The instructions for installing latest rust can be found here.

Then you just need to invoke the following command from inside the CLI directory:

$ cargo build --release

the screenly binary will be located in target/release directory.

To utilize an alternative API server (non-production), employ the API_SERVER_NAME environment variable for configuring the desired API server URL. Available options include: 'prod', 'local', and 'stage'.

$ API_SERVER_NAME=local cargo build --release
## GitHub Action

Our CLI is also available as a GitHub Action workflow.

## Inputs

### `screenly_api_token`

**Required** The Screenly API token for your team. You can retrieve this by going to `Settings` -> `Team` -> `Tokens`. Note that API tokens are limited in scope to your team.

You should use a [GitHub Action Secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets) to store this rather than hard coding this in your code base.

### `cli_commands`

**Required** This is the command you want to pass on, such as `screen list`.

### `cli_version`

Use this option to override the CLI version used by the Action. Must point to a [valid release](https://github.com/Screenly/cli/releases).

## Example usage

```yaml
uses: screenly/cli@master
with:
  screenly_api_token: ${{ secrets.SCREENLY_API_TOKEN }}
  cli_commands: screen list

Protobuf generation

There is a signature.proto protobuf file used for file signature generation. pb_signature.rs is generated from signature.proto using the following command:

$ cargo install protobuf-codegen
$ protoc --rust_out . signature.proto
$ mv signature.rs src/pb_signature.rs

Protocol Buffers (Protobuf) Generation

In order to generate the file signature, we utilize the signature.proto protobuf file. The corresponding Rust file, pb_signature.rs, is derived from signature.proto using the following steps:

Install the Protobuf code generator for Rust:

$ cargo install protobuf-codegen

Generate the Rust code from signature.proto:

$ protoc --rust_out . signature.proto

Move the generated signature.rs to the appropriate source directory (src/pb_signature.rs in this case):

$ mv signature.rs src/pb_signature.rs