Download as PDF, PPTX
![Step12:!
show the log!
!
see how the requests are coming in !
a great step for debugging!
$docker logs (docker ps for service names)
$docker-compose logs [service_name]](https://image.slidesharecdn.com/cloud66workshophandoutsfinal-160330124518/75/Cloud66-workshop-handouts-15-2048.jpg)
![Step 13:!
speedup baking by
scaling the minions!
!
place some order in the bakery shop ;-)!
scale some minions!
!
!
!
!
see how the backing is speed up!
!
$docker-compose scale [minion_service_name]=5](https://image.slidesharecdn.com/cloud66workshophandoutsfinal-160330124518/75/Cloud66-workshop-handouts-16-2048.jpg)
![Step 5: !
setup DNS!
check the UI for the new IP address of your docker
cluster.!
edit your /etc/hosts file to point the following URL’s!
[ip_address] www.microservices101.io!
[ip_address] api.microservices101.io!
[ip_address] cms.microservice101.io!
!
!
!](https://image.slidesharecdn.com/cloud66workshophandoutsfinal-160330124518/75/Cloud66-workshop-handouts-28-2048.jpg)
![scale a minion
play with scaling others and list all services:
Step 10:!
scale up using CX!
$cx services scale -s [your stack] minion_bagel 5
$cx services list -s [your stack]](https://image.slidesharecdn.com/cloud66workshophandoutsfinal-160330124518/75/Cloud66-workshop-handouts-33-2048.jpg)
Uploaded byCloud 66
Cloud66 workshop handouts
This document provides a step-by-step guide for deploying web applications using Docker containers, covering necessary account setups and installation processes. It includes detailed instructions for creating a development machine on DigitalOcean, building Docker images, running applications, initializing databases, and scaling services. Additionally, it details the process for using Cloud 66 to manage Docker stacks, DNS setup, and version control tasks for the application code.
More Related Content
![[React Native Tutorial] Lecture 5: Input and State](https://cdn.slidesharecdn.com/ss_thumbnails/l5-react-native-input-state-160913041941-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Cloud66 workshop handouts
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Cloud66 workshop handouts
- 1. How to DeployWeb Apps with Docker containers! Workshop Resources!
- 2.
- 3. Step1: ! create DigitalOceanaccount! ! go to https://cloud.digitalocean.com/registrations/new! and create a new account! ! Please use Promo Code: CLOUD66, to receive a $10 Credit. !
- 4. Step 2: ! createCloud 66 account! ! go to https://app.cloud66.com/users/sign_up! and create a new account!
- 5. Step 3:! create aremote development machine! ! go to https://cloud.digitalocean.com/droplets/new! use the One-click App tab! choose Docker 1.10.3 on 14:04 choose size $40/month region London press create you’ll get the login information mailed to you! !
- 6. Step 4:! log intodevelopment machine! ssh to your new server open terminal use the password in the DigitalOcean email you will be asked to change your password $ssh root@<your ip>
- 7. Step 5:! install docker-compose! outputshould be : docker-compose version: 1.6.2 $curl -L https://github.com/docker/compose/releases/download/1.6.2/ docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose $chmod +x /usr/local/bin/docker-compose $docker-compose —version
- 8. Step 6:! fork thebakery example and pull the code! go to Github.com fork https://github.com/cloud66-samples/microservices_101 create a a home-directory for the app pull the code $mkdir /home/app $cd /home/app $git clone https://github.com/<your github account>/microservices_101
- 9. go to thebakery/bricksandmortar folder and change the IP address (of your new server) of the API to be used Step 6½:! change the ip! $vi /home/app/microservices_101/bakery/bricksandmortar/Dockerfile.development ENV COUNTER_ADDRESS <your ip address>:8000
- 10. Step 7:! build allthe images! $ cd /home/app/microservices_101/bakery go to the bakery folder build all the images (takes approx. 10 minutes) $docker-compose build
- 11. Step 8:! run theapplication! ! $docker-compose up -d
- 12. Step 9:! init thedatasource with an on/off command! create the DB migrate the DB schema $docker-compose run counter rake db:create $docker-compose run counter rake db:migrate
- 13. Step 10:! list allthe running containers! $docker ps $docker-compose ps
- 14. Step 11:! play withthe demo! ! check docker-compose.yml to find out on which port the services are running! https://docs.docker.com/compose/compose-file/!
- 15. Step12:! show the log! ! seehow the requests are coming in ! a great step for debugging! $docker logs (docker ps for service names) $docker-compose logs [service_name]
- 16. Step 13:! speedup bakingby scaling the minions! ! place some order in the bakery shop ;-)! scale some minions! ! ! ! ! see how the backing is speed up! ! $docker-compose scale [minion_service_name]=5
- 17. Step 14:! speedup updateby scaling the counter! ! $docker-compose scale counter=2
- 18. Step 15:! speedup updateby scaling the counter! ! lets scale our API! why does it fail? $docker-compose scale counter=2
- 19. Step 16:! edit thework time of a minion (language of choice) and build/ restart! edit the code and change the minion time You can edit on your local machine and push the changes to github and pull them into the remote machine, or edit the code directly on the remote machine. after editing; rebuild the service and restart the service docker-compose will pickup the change $docker-compose build minion_service_name $docker-compose up -d minion_service_name
- 20. Step 17:! development ofa service ! stop the service ! go to the source folder of a service! look at the docker-compose.ml! we mount the host volume. you can edit and change code and start stop when need! ! ! ! ! edit the service and just run only the ! ! ! ! (no need for building)! $docker-compose stop minion_service_name $docker-compose run minion_service_name
- 21. Step 18:! build/restart service! doneediting and debugging? build the service ! ! ! ! ! run it again! ! $docker-compose build minion_service_name $docker-compose up -d minion_service_name
- 22. Step 19:! show memoryusage! ! if you want to see how the memory is getting used:! run memory usage! ! ! ! ! ! ! ! $docker stats `docker ps | awk '{print $NF}' | grep -v NAMES`
- 23.
- 24. Step 1:! add DOas your cloud provider! ! go to https://app.cloud66.com/clouds and add digital ocean as the cloud provider!
- 25. Step 2:! create anew Docker stack! go to your cloud 66 account and create a Docker stack; give the stack a name and use the service.yml in .cloud directory from your repository! paste the service.yml in the advanced tab and hit NEXT !
- 26. Step 3: choicecloud provider (DO) and start deploy! run on digital ocean using region: london / 20gb / 2cpu run mysql and rabbitmq on the same server! and hit deploy
- 27. Step 4:! explore service.yml duringwaiting! help.cloud66.com/building-your-stack/docker-service- configuration!
- 28. Step 5: ! setupDNS! check the UI for the new IP address of your docker cluster.! edit your /etc/hosts file to point the following URL’s! [ip_address] www.microservices101.io! [ip_address] api.microservices101.io! [ip_address] cms.microservice101.io! ! ! !
- 29. Step 6: ! Seeyou bakery in action! ! visit www.microservice101.io!
- 30. Step 7:! use LiveLogs to see the logs of the services!
- 31. Step 8:! scale upthe minion process for the UI!
- 32. Step 9:! install cx! $curl-sSL https://s3.amazonaws.com/downloads.cloud66.com/cx_installation/cx_install.sh | bash $gcx stacks list install out CX tool belt go to your remote development machine (not the one created with C66) please register the tool belt check if you can see your new stack
- 33. scale a minion playwith scaling others and list all services: Step 10:! scale up using CX! $cx services scale -s [your stack] minion_bagel 5 $cx services list -s [your stack]
- 34. Step 11:! change somecode of the minion and push it to your repo! Commit your changes and push those changes to github.! Edit the service.yml to use build grid instead of pulling images from Docker Hub.! Build and publish only that service.!