Notploy

Schedules

Cron jobs that run a shell command inside a deployed service. Generated from the `notploy` command surface.

Cron jobs that run a shell command inside a deployed service.

notploy schedule exposes 6 commands. They map one-to-one onto the schedule.* API operations, so anything reachable from the dashboard is reachable from here.

Run notploy schedule --help to list these commands in your terminal, or notploy schedule <command> --help for a single command.

Commands

notploy schedule create

Calls POST /api/trpc/schedule.create.

notploy schedule create --name <value> --cronExpression <value> --command <value> [options]
OptionTypeRequiredAllowed values
--scheduleId <value>stringNo—
--name <value>stringYes—
--description <value>stringNo—
--cronExpression <value>stringYes—
--appName <value>stringNo—
--serviceName <value>stringNo—
--shellType <value>stringNobash, sh
--scheduleType <value>stringNoapplication, compose, server, notploy-server
--command <value>stringYes—
--script <value>stringNo—
--applicationId <value>stringNo—
--composeId <value>stringNo—
--serverId <value>stringNo—
--organizationId <value>stringNo—
--enabled [boolean]booleanNo—
--no-enabledbooleanNo—
--timezone <value>stringNo—
--createdAt <value>stringNo—
--profile <name>stringNo—

notploy schedule delete

Calls POST /api/trpc/schedule.delete.

notploy schedule delete --scheduleId <value> [options]
OptionTypeRequiredAllowed values
--scheduleId <value>stringYes—
--profile <name>stringNo—

notploy schedule list

Calls GET /api/trpc/schedule.list.

notploy schedule list --id <value> --scheduleType <value> [options]
OptionTypeRequiredAllowed values
--id <value>stringYes—
--scheduleType <value>stringYesapplication, compose, server, notploy-server
--profile <name>stringNo—

notploy schedule one

Calls GET /api/trpc/schedule.one.

notploy schedule one --scheduleId <value> [options]
OptionTypeRequiredAllowed values
--scheduleId <value>stringYes—
--profile <name>stringNo—

notploy schedule run-manually

Calls POST /api/trpc/schedule.runManually.

notploy schedule run-manually --scheduleId <value> [options]
OptionTypeRequiredAllowed values
--scheduleId <value>stringYes—
--profile <name>stringNo—

notploy schedule update

Calls POST /api/trpc/schedule.update.

notploy schedule update --scheduleId <value> --name <value> --cronExpression <value> --command <value> [options]
OptionTypeRequiredAllowed values
--scheduleId <value>stringYes—
--name <value>stringYes—
--description <value>stringNo—
--cronExpression <value>stringYes—
--appName <value>stringNo—
--serviceName <value>stringNo—
--shellType <value>stringNobash, sh
--scheduleType <value>stringNoapplication, compose, server, notploy-server
--command <value>stringYes—
--script <value>stringNo—
--applicationId <value>stringNo—
--composeId <value>stringNo—
--serverId <value>stringNo—
--organizationId <value>stringNo—
--enabled [boolean]booleanNo—
--no-enabledbooleanNo—
--timezone <value>stringNo—
--createdAt <value>stringNo—
--profile <name>stringNo—

On this page