Skip to main content

Push

The push command facilitates the distribution of the packaged application to the ProconTEL 4 platform.

pct push [--alias <alias>] [-f, --file <path_to_procontel_file>] [--no-build] [-t, --tag <tags separated by comma>]

Parameters:

  • -a/--alias: (Optional) The alias or identifier of the application being pushed. If not specified, all applications defined in the .procontel file will be push.

  • -f/--file: (Optional) Specifies the path to the .procontel configuration file. If not provided, the CLI looks for the file in the current folder.

  • --no-build: (Optional) When provided, the build process is skipped before pushing the application(s). Useful for scenarios where you're certain the build is updated and you just want to push.

  • -t/--tag: (Optional) Assign tags to the app template revision created during the push operation. Separate multiple tags with commas. When provided, these tags replace the tags defined in the .procontel file.

Tag restrictions​

  • A comma is always treated as a tag separator, so it cannot be part of a tag. Wrapping the value in quotes does not change this: --tag "Release 1.0, hotfix" creates two tags, Release 1.0 and hotfix.
  • At most 10 tags per app template revision.
  • Each tag can have at most 30 characters.
  • Leading and trailing spaces are removed, empty entries are ignored and duplicates are pushed only once.

If any restriction is violated, the CLI prints which tag is invalid and stops before building or uploading anything. Tags can also be defined in the .procontel file.

Examples:​

  1. Push a single application:

    pct push --alias basic-app

  2. Push all applications from a file:

    pct push

  3. Push without building:

    pct push --alias basic-app --no-build

  4. Push with additional tags:

    pct push --alias basic-app --tag tag1,tag2,tag3

  5. Push with tags containing spaces:

    pct push --alias basic-app --tag "Release 1.0,Hotfix for login"