I propose that we create a Docker image for the everactive-cli that enables users to run the CLI without needing to install it in their local environment. By using a Dockerized version of the everactive-cli, users can simply pull and build the image, then alias their local everactive-cli (or similar command) to run the commands via the Docker container. CLI upgrade? Just pull the new image, and you're set!
As an example - AWS offers their AWS CLI as a Docker image:
Though I am admittedly a containerization zealot when it comes to local development, I think offering a Dockerized everactive-cli option will benefit both us and our users. Running code via a controlled container environment minimizes the potential for edge case and individualized problems due to local environment settings - reducing headaches & frustrations for our users and support time for us.
I propose that we create a Docker image for the everactive-cli that enables users to run the CLI without needing to install it in their local environment. By using a Dockerized version of the everactive-cli, users can simply pull and build the image, then alias their local
everactive-cli(or similar command) to run the commands via the Docker container. CLI upgrade? Just pull the new image, and you're set!As an example - AWS offers their AWS CLI as a Docker image:
Though I am admittedly a containerization zealot when it comes to local development, I think offering a Dockerized everactive-cli option will benefit both us and our users. Running code via a controlled container environment minimizes the potential for edge case and individualized problems due to local environment settings - reducing headaches & frustrations for our users and support time for us.