All configuration should be automated through Puppet/Ansible/Salt/whatever

[maggix]

Right now only the setup of MongoDB is automated through Puppet.

Ideally, in the end all the setup of the application should be automated. Things like:

• Installing DB
• Installing all dependencies
• Installing server software (git, pip, virtualenv)
• Starting the service python wsgi.py and ensuring that is restarted

[stonaz]

On 06/02/2014 05:38 PM, Giovanni Maggini wrote:

Right now only the setup of MongoDB is automated.

Ideally, in the end all the setup of the application should be automated. Things like

• Installing DB
• Installing all dependencies
• Installing server software (git, pip, virtualenv)
• Starting the service |python wsgi.py| and ensuring that is restarted

— Reply to this email directly or view it on GitHub https://github.com/codeforeurope/change-by-us-3/issues/1.

Hi Giovanni, we have made a similar work on this repository, using Fabric: https://github.com/ninuxorg/nodeshot

Here is the link to the fabfile that manages dependencies, DB creation, virtual env, etc.. https://github.com/ninuxorg/nodeshot/blob/master/INSTALL/fabfile.py

Maybe it can give you some inspiration.

Best Stefano

[maggix]

Very clean fabfile.py :) Makes me want to use it. Now it's a hard choice between that and stuff like Ansible & co. Also because I would like to reuse as much as possible to also automate https://github.com/codeforeurope/change-by-us

On Tue, Jun 3, 2014 at 2:34 PM, stonazzi notifications@github.com wrote:

On 06/02/2014 05:38 PM, Giovanni Maggini wrote:

Right now only the setup of MongoDB is automated.

Ideally, in the end all the setup of the application should be automated. Things like

• Installing DB
• Installing all dependencies
• Installing server software (git, pip, virtualenv)
• Starting the service |python wsgi.py| and ensuring that is restarted

— Reply to this email directly or view it on GitHub https://github.com/codeforeurope/change-by-us-3/issues/1.

Hi Giovanni, we have made a similar work on this repository, using Fabric: https://github.com/ninuxorg/nodeshot

Here is the link to the fabfile that manages dependencies, DB creation, virtual env, etc.. https://github.com/ninuxorg/nodeshot/blob/master/INSTALL/fabfile.py

Maybe it can give you some inspiration.

Best Stefano

— Reply to this email directly or view it on GitHub https://github.com/codeforeurope/change-by-us-3/issues/1#issuecomment-44958355 .

Giovanni Maggini Twitter: @maggix giovanni.maggini@gmail.com Skype:maggix04 IT +39 339 2239235 | NL +31 6 81 31 91 96

[stonaz]

On 06/03/2014 04:12 PM, Giovanni Maggini wrote:

Very clean fabfile.py :) Makes me want to use it. Now it's a hard choice between that and stuff like Ansible & co. Also because I would like to reuse as much as possible to also automate https://github.com/codeforeurope/change-by-us

Ansible is probably more structured, while Fabric has that 'artisanal' flavour. Feel free to use it, if you find it useful. You can find docs about it here: http://nodeshot.readthedocs.org/en/latest/topics/automated_install.html

Beware of all those

with hide('stdout', 'stderr'): Hiding stdout could mask user input requests that you would not expect ( they can raise in different conditions )

Cheers Stefano

[maggix]

:+1: Congratulations on the great work on the ninux project. Your fabfile gave me a push in order to work with Fabric... but on a different app!! :) In fact I automated the deployment of Change-by-us (in the other repo) by trying to improve the existing fabfile.py.