playrote.play.v1

aankurrawat/env-example-scaffolderv4.1.0Public

Env example scaffolder

DevOps & Container Optimization Engine for env-example-scaffolder: Scans build artifacts, optimizes Dockerfile multi-stage layers, and automates CI/CD deployments.

  • Published 4 Sep 2026
  • Downloads 0
  • Needs rote 0.62.0+
  • Digest sha256:d7544d52fcef…
  • Reference ankurrawat/env-example-scaffolder@4.1.0

Before you run it

Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.

No services, browser, or local tools are declared. Only the rote CLI is needed.

Inputs2, all optional

rote asks for these before running and shows the defaults it will use.

  • Build Directorybuild_output_dir

    Directory containing compiled build assets and binaries

    optionalstringdefault ./distcustom value allowed
  • Max Package Size (MB)max_bundle_size_mb

    Maximum allowable package deployment size threshold in Megabytes

    optionalnumberdefault 50custom value allowed

What it changes

No write operations are declared in this version's manifest.

Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.

Runtime details
  • rote CLIversion 0.62.0 or newer
  • Servicesnone declared
  • Digestsha256:d7544d52fcefc79d797caa17ec57e88f2861d60ac427766b3a823b44595336d6
  • Archive size1815 bytes
  • Published2026-09-04T09:18:00.778063+00:00
  • Published withrote 0.77.1

Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.

A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.