Simplify deploying a local version

[peol]

We've had multiple requests to offer an offline/local built version. Current thinking:

• Use Docker images (qlikcore/catwalk:latest is pushed when we update catwalk.core.qlik.com, qlikcore/catwalk:version whenever there's a release)

This way, the user does not have to manually check out code and build it, bundle it as a Docker image, and re-deploy.

[MACKAT05]

As jazzed as I am about Docker. There are a lot of smaller enterprise orgs who don't or can't use it, but also have loads of data security issues where they would want to run this locally.

Is there a more traditional feeling route to this app being localized.
perhaps run it as a service using the node-windows package?

[peol]

@MACKAT05 The current README instructions include how to build/run it locally without Docker, I don't see how packaging it as a node-windows package would reduce security concerns, it would still need a Node.js/npm package run-time? Or are the concerns mainly around Docker?

[MACKAT05]

The concern is around Docker.
Docker is not available in all situations. In particular where there are skill constraints or concerns with exposing PHI to untested systems. My experience has been more the former and not the latter.

I suppose in retrospect my concern was not clear given your suggestion.
Having tried; I have found that running locally as described in the ReadMe requires manual intervention for server restarts or Hangs, so there ends up being a lot of down time and low adoption.

Running it on docker is desirable as a generic web-service in its own container,
but being able to treat it as a windows-service on existing qlik sense proxy node
(where node.js is already present, and is already white-listed by necessity)
is better for Admins whom may not be skilled or versed with docker but being Qlik sense admins belong to a set of people whom understand windows service conventions.