CLI only process mangement mode

[dai-yamashita]

Regarding deployex, when you want to use it in production environments, you might not want to expose the management interface externally on the web.
In such cases, having a CLI UI like pm2 or command-line management would be extremely convenient. Is implementing such functionality being considered?

[thiagoesteves]

Hi @sena-yamashita , thanks for bringing this topic. For the time being, this functionality is not being considered, the current effort is focused in 2 main topics: deploy handling and UX/UI, but I do see a great value in programmatically configure and handle it. Since you brought it, do you have any specific requirement?

[dai-yamashita]

@thiagoesteves ,Thank you for your reply.

Setting up a release-ready WEBUI in a production environment is often difficult due to security concerns and other factors. Therefore, having various commands like pm2, as you suggested, would be absolutely perfect.

https://github.com/Unitech/pm2

To list all running applications:

$ deployex list

Managing apps is straightforward:

I would be truly happy if this could be hot-upgraded.

$ deployex stop     <app_name|namespace|id|'all'|json_conf>
$ deployex restart  <app_name|namespace|id|'all'|json_conf>
$ deployex delete   <app_name|namespace|id|'all'|json_conf>

To have more details on a specific application:

$ deployex describe <id|app_name>

To monitor logs, custom metrics, application information:

$ deployex monit

Log Management

To consult logs just type the command:

$ deployex logs

Examples:

$ deployex logs APP-NAME       # Display APP-NAME logs

[thiagoesteves]

Ok, that sounds like a cool feature, never bumped in pm2. For now, DeployEx only has an installer script and I have thinking about extending the script or create another binary installer using Go or even elixir to do it. I will probably return to this subject soon and your suggestions will be very valuable.

Many thanks

[thiagoesteves]

Regarding this feature, there are some new commands being added to the installer script that will pivot the path to achieve the CLI management mode. The next release will be able to uninstall and hotupgrade:

    echo "Usage:"
    echo "  $0 --install [config_file] [--dist <base_url>]"
    echo "  $0 --update [config_file] [--dist <base_url>]"
    echo "  $0 --uninstall [config_file]"
    echo "  $0 --hot-upgrade <release_path> [config_file]"
    echo "  $0 --help"
    echo
    echo "Options:"
    echo "  --install [config_file]   Install an application using a config file"
    echo "                            (default: ${DEFAULT_CONFIG_FILE})"
    echo "  --update [config_file]    Update ONLY the deployex application using a config file"
    echo "                            (default: ${DEFAULT_CONFIG_FILE})"
    echo "  --uninstall [config_file] Completely remove deployex from the system"
    echo "                            (default: ${DEFAULT_CONFIG_FILE})"
    echo "  --hot-upgrade <release_path>    Perform hot upgrade with downloaded release tarball"
    echo "                                  [config_file] (default: ${DEFAULT_CONFIG_FILE})"
    echo "                                  Requires: RELEASE_COOKIE environment variable"
    echo "  --dist <base_url>         Base URL for downloading releases"
    echo "                            (default: ${DEFAULT_DIST_URL})"
    echo "  --help                    Print help"

Also, a new ticket was created to modify the script to a multi platform binary ISSUE-194. Thanks for the feedback @sena-yamashita.