This document outlines the typical life cycle of a ruby project in a startup from initial development through deployment and operations. It begins with discussing startups, minimum viable products, and getting user feedback. It then describes the evolution of deployment from using bash scripts to using load balancers and tools like Ansible to enable easy deployment. It also discusses the devops movement and trends like constant integration, testing, and automated deployments. Specific techniques like using Docker, Redis, and cron jobs for a pet project API are outlined. Finally, it discusses next steps like continuous integration, deployment, and delivery and improving the architecture further.

1. The life cycle of a ruby project in a startup
perspective
Ruby applica+ons in real life
Ivan Santos
Docker Meetup Alagoas

2. Ivan Santos
2

3. GUIA DO TRABALHO REMOTO
h+p://guiadotrabalhoremoto.com.br

4. Agenda
4
- Startups, MVP, Feedbacks
- Deployment Evolution
- Pet Project
- Architecture
- Hands on
- Next steps

5. Startups, MVP, Feedbacks
5

6. In data we trust!
6
IF WE DON’T KNOW WHERE WE WANT TO GO, WE’RE
NOT GOING ANYWHERE.

7. In data we trust!
7

8. Pray. Trust. Wait.
8
The APT-GET/BASH SCRIPT era.

9. Houston, we have a problem!
9

10. Load Balancers And Easy Deployment
10

11. Provisioning
11
~$ ansible-playbook -i production playbook.yml
4-10 minutes

12. DevOps Movement
12
- Constant feedback
- Tests
- Automated Deployment
- Better Production delivery
- 0 time deployments and Canary Release

13. OS-level virtualizaNon
13

14. Pet Project
14
larica.club - API
Ruby
Rails
Grape
Sidekiq (Redis) (Workers)
Whenever (Cron Jobs)

15. Pet Project - Proxy
15

16. Pet Project -Architecture
16

17. Hands On
17
Playing with Docker

18. Next Steps
18
ConNnuous IntegraNon
ConNnuous Deployment
ConNnuous Delivery (with approval tag)
Proxy with auto scale
BUNDLE PATH with volumes
Extract Docker config

19. 19
I'm not happy unless I'm being
challenged.

20. Thank You
@pragma+civan