cli
cli copied to clipboard
Command Line Interface (CLI) and GitHub Actions workflow for Screenly.
It does nothing in the emulator. ## What does this PR do? ## GitHub issue or Phabricator ticket number? ## How has this been tested? ## Checklist before merging -...
Minor 1.0.1 release with debug logs accessible in release build via RUST_LOG=debug env var.
Based on the v3 API documentation, we're not returning the full object. Most prominently, we're missing the following data points: * is_enabled * priority
So let's say you are working on a local app and introduce a new setting to `screenly.yml` with `mock-data.yml` present. It is then very easy to lose a lot of...
Error when trying to run edge app emulator, but working fine when createing and deploying the edge app. ``` > screenly edge-app run thread 'main' panicked at src/cli.rs:823:48: Failed to...
- Remove informal phrasing - Add article "the" before "version" - Improve optional step formatting - Fix version tag typo (v1.0.h6 → v1.0.6)
They were disabled because unlike Linux on Macos tests of the following nature were failing: test_x_when_env_is_set_overrides... set_env(...) work() // set_env was not getting picked up
It would be better to include settings like `theme`, `screenly_color_light`, and `screenly_color_dark` in the generated `screenly.js` so that users won't have to put those manually in `mock-data.yml`.
Ideally, we would want something like the following: ```bash screenly edge-app setting set setting_1= setting_2= ... setting_n= ```