production, npm install , stop, symlink and restart.
I've been trying to use containers in some way, mainly as a proof of concept. Please help me with the following deployment scenario:
Build and test a running container in my development environment, then upload it (somehow, i'm not familiar w/containers yet) to google private containter registry. Then on my production machine download the container (again, somehow), stop the previous one and start the new one.
Does this make sense? As you can see i'm on GCP and using GCE instances.
could tell yo eaxctly what to do with AWS lol. but on the GCE instance, you'd only need to install docker and login to your prviate docker registery
Hola Rubén. What kind of services do you need to deploy? On docker you can have a private repo, called registry. You just need to deploy it somewhere, create your images and push and pull them there. It has an API. So just test your apps, make them work with your customs configs, and upload em to the registry. By the way, a nice introduction to how do containers work, could me a Mesos-Marathon stack. It is quite visual, and you will ensure that your apps are running well. Just my point of view.
Обсуждают сегодня