Skip to main content

vertx command line parameters

How to pass command line parameters to "vertx run"


I'm using continuous delivery and need to checkout a git branch then launch the verticle with a parameter.
For example:
  1. I chekcout the "demo" git branch
  2. I deploy it to the target
  3. I remotely run the verticle with "vertx run 'demo'" (this actually doesn't work, but it illustrates my needs)

The solution: use system environment variables

The documentation is mentionning it, but it was not straight to me, so here is precisely how I did:

package org.rktmb.vertx
// ...
import io.vertx.config.ConfigStoreOptions;
import io.vertx.config.ConfigRetriever;
import io.vertx.config.ConfigRetrieverOptions;
// ...

public class MainVerticle extends SyncVerticle {
    public void start(Future startFuture) throws Exception {
 // ...
        ConfigStoreOptions jsonEnvConfig = new ConfigStoreOptions().setType("env")
            .setConfig(new JsonObject().put("keys", new JsonArray().add("VXBRANCH").add("VXPORT")));
        ConfigRetrieverOptions myOptions = new ConfigRetrieverOptions().addStore(jsonEnvConfig);
        ConfigRetriever myConfigRetriver = ConfigRetriever.create(vertx, myOptions);
        myConfigRetriver.getConfig(asyncResults -> System.out.println(asyncResults.result().encodePrettily()));
 // ..
Then, when running the verticle
VXPORT="123" VXBRANCH="prod"  vertx run --classpath=target/test-1.0.0-SNAPSHOT-fat.jar org.rktmb.vertx.MainVerticle
This displays:
  "VXBRANCH" : "prod",
  "VXPORT" : 123.0

If I ever change the environment variables: the rendered JSON changes accordingly.

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM