Well, using docker compose it was pretty easy -- no https though.
Create a docker-compose.yml file like:
- "JAVA_OPTS=-Dserver -Dd64 -Xms1024m -Xmx5g -XX:+UseNUMA -XX:+UseConcMarkSweepGC"
You do need to specify you want to use Java 8 runtime.
Not sure I needed the JAVA_OPTS but I saw them used in another forum thread.
You create folders in the directory where the yaml file is for the two ThingWorx storage folders. You also copy the thingworx.war file from the developer zip.
You expose the 8080 port from the container to localhost.
Run this with:
Wait about a minute and then ThingWorx is up and running.
This is so easy that the developer release docs should recommend this as the easy-button.
Interested to hear if this works for anyone else.
I would agree that docker is a great approach for testing, teaching, and learning ThingWorx. You can spin up a test ThingWorx instance in a matter of seconds (literally) with a quick `docker run` command and can even spin up PostgreSQL, MySQL, etc to pair with ThingWorx for testing various scenarios.
We use docker build files instead and then push the image to a private repository for other people in our organization to use. For them, it's a one-line command to run a new ThingWorx instance.