Pac-Man Node.js application
Using docker-compose
you can start a local development environment. This environment will bind mount the applications
src
directory into the container and then uses nodemon
to detect changes and rebuild the application live.
Start the local development enviornment
cd pacman-nodejs
bin/linux/development-compose-up.sh
Stop the local development enviornment
cd pacman-nodejs
bin/linux/development-compose-up.sh
Using docker-compose
you can start a local production environment. This environment will bind mount the applications
src
directory into the container but will NOT detect changes and rebuild the application live.
Start the local production enviornment
cd pacman-nodejs
bin/linux/production-compose-up.sh
Stop the local production enviornment
cd pacman-nodejs
bin/linux/production-compose-up.sh
This application can be deployed on Kubernetes or Swarm using the YAML files in thier respective directories
(kubernetes/cluster/
or swarm/
). The repository is currently setup to use the Mirantis Docker Enterprise
Demo environments. This includes a Jenkins server and all of the automation to deploy the application onto
the selected cluster.
git clone https://github.com/mirantis-field/pacman-nodejs.git
git checkout -b <mirantis.local username>
git push --set-upstream origin <mirantis.local username>
The new branch will automatically be detected by Jenkins and deployed onto the default cluster using the default
orchestrator, specified in the Jenkinsfile
.
To switch the deployment cluster, you can set the value of TARGET_CLUSTER_DOMAIN
in the Jenkinsfile
.
For available options check the Presales Docker Enterprise Environment wiki.
To switch between Kubernetes and Swarm, you can set the value of ORCHESTRATOR
in the Jenkinsfile
.
Available options are "kubernetes"
or "swarm"
To switch between Kubernetes and Swarm, you can set the value of KUBERNETES_INGRESS
in the Jenkinsfile
.
Available options are "ingress"
or "istio_gateway"