Notploy

Ports

Publish container ports directly, without routing them through a domain. Generated from the `notploy` command surface.

Publish container ports directly, without routing them through a domain.

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

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

Commands

notploy port create

Calls POST /api/trpc/port.create.

notploy port create --publishedPort <value> --publishMode <value> --targetPort <value> --protocol <value> --applicationId <value> [options]
OptionTypeRequiredAllowed values
--publishedPort <value>numberYes—
--publishMode <value>stringYesingress, host
--targetPort <value>numberYes—
--protocol <value>stringYestcp, udp
--applicationId <value>stringYes—
--profile <name>stringNo—

notploy port delete

Calls POST /api/trpc/port.delete.

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

notploy port one

Calls GET /api/trpc/port.one.

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

notploy port update

Calls POST /api/trpc/port.update.

notploy port update --portId <value> --publishedPort <value> --publishMode <value> --targetPort <value> --protocol <value> [options]
OptionTypeRequiredAllowed values
--portId <value>stringYes—
--publishedPort <value>numberYes—
--publishMode <value>stringYesingress, host
--targetPort <value>numberYes—
--protocol <value>stringYestcp, udp
--profile <name>stringNo—

On this page