Skip to content
This repository has been archived by the owner on Feb 28, 2018. It is now read-only.

Automate deploy with Docker #53

Closed
cuducos opened this issue Nov 26, 2016 · 21 comments
Closed

Automate deploy with Docker #53

cuducos opened this issue Nov 26, 2016 · 21 comments

Comments

@cuducos
Copy link
Collaborator

cuducos commented Nov 26, 2016

Now we have a Docker structure, so we can think about how to use that to automate the deploy.

Ideally a piece of code to automate provision is much appreciated ; )

@vmesel
Copy link

vmesel commented Dec 7, 2016

I think it's already done and this issue should be closed @cuducos !

@cuducos
Copy link
Collaborator Author

cuducos commented Dec 7, 2016

@gomex might be working on or planning something in that direction — you both could collaborate with each other if that's the case ; )

@gwmoura
Copy link

gwmoura commented Dec 8, 2016

@vmesel You have one idea, how to deploy? Today we need to deploy 4 services (maybe 3):

  • jarbas - django app
  • elm - nodejs
  • web - nginx
  • db - postgresql

@pedrommone
Copy link
Contributor

I think a Ansible is the easiest way to provision it right now, since the stack is very tiny. How are you planning it @gomex?

@gomex
Copy link
Contributor

gomex commented Dec 9, 2016

I was thinking about using ansible to create the docker host and to run the docker-compose there. What you think about?

@pedrommone
Copy link
Contributor

pedrommone commented Dec 9, 2016

@gomex it's the easiest way and probably, the best way for now.

@gwmoura
Copy link

gwmoura commented Dec 13, 2016

Hi, guys how this is running?

@cuducos
Copy link
Collaborator Author

cuducos commented Dec 14, 2016

@gwmoura Apparently nobody's working on that — ages ago I started a branch called ansible but back then it was focused on deploying without Docker. I'd be happy to pair on that to sort that out, but I need guidance from one of you guys.

@gwmoura
Copy link

gwmoura commented Dec 14, 2016

@cuducos we can pair, but basically is use the ansible to install docker on server and run docker-compose up.

We can follow the steps on this link: https://docs.docker.com/compose/production/

  • Create a jarbas-production.yaml
  • Define tasks to be runned before app run
  • Define strategy for no downtime 😄

    to deploy a container is necessary stop one before start another - 😅

@cuducos
Copy link
Collaborator Author

cuducos commented Dec 14, 2016

Great material. I have the feeling that I will take a lot of time with that with the less basic stuff (such as keep sensible information on the environment etc). It's not my priority right now but I'd make it a priority if anyone can pair with me to speed thing up. Otherwise I'll try to build a Dockerfile for Rosie, so Rosie can live in the same server as Jarbas, easily deployed with Docker ; )

@gomex
Copy link
Contributor

gomex commented Dec 22, 2016

I can pair with you. I already have a ansible role to create a droplet on Digital Ocean with Docker host installed and now we just need to configure a role to start docker there.

@cuducos
Copy link
Collaborator Author

cuducos commented Dec 22, 2016

Great! When does it work to you? I'm basically free weekdays, whole day, except 2-4pm ; )

@gomex
Copy link
Contributor

gomex commented Dec 22, 2016

I am free weekdays too, but in the night is better for me :)

@gomex
Copy link
Contributor

gomex commented Dec 23, 2016

I am finish to clean the code and send I PR with a proposal for create droplets on Digital Ocean using ansible.

@gomex
Copy link
Contributor

gomex commented Dec 23, 2016

I am doing that in my fork, you can follow there:

https://travis-ci.org/gomex/jarbas

My problem now is about keep together the old deploy code of travis and the new proposal to use ansible, because ansible is not ok yet to use 3.5 python language :( I changed to 2.7 and got problem with that:

coverage run manage.py test -v 3
Couldn't read config file .coveragerc: File contains no section headers.
file: .coveragerc, line: 1
'  [run]\n'
The command "coverage run manage.py test -v 3" exited with 1.

@cuducos
Copy link
Collaborator Author

cuducos commented Dec 23, 2016

Unfortunately we need Python 3 to run Jarbas. If you start travis in Python 2.7, you can install (if needed, have to check Ubuntu/Debian version) python3 and run all the commands with python3 instead of python (for example python3 manage.py test instead of python manage.py test) — sounds reasonable?

@gomex
Copy link
Contributor

gomex commented Dec 25, 2016

@cuducos today the jarbas is deployed in only one machine or a cluster?

@cuducos
Copy link
Collaborator Author

cuducos commented Dec 25, 2016 via email

@lipemorais
Copy link
Contributor

I believe that the next step after the PR about make Docker work for Jarbas development(a.k.a #163 ) could this one. What do you think @cuducos ?

@cuducos
Copy link
Collaborator Author

cuducos commented May 16, 2017

So far so good @lipemorais — I'm gonna test and (hopefully) merge #163 today and then we can look into deploy with Docker <3

@cuducos
Copy link
Collaborator Author

cuducos commented Jun 13, 2017

Closed in favor of #191

@cuducos cuducos closed this as completed Jun 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants