The reason why I put it in deploy is that it needs to install any new
requirements that have been added in the meanwhile. I don't want to run a
full-on setup for that.

Thoughts?

Adi


On 13 March 2014 11:41, Petrus Janse van Rensburg
<notifications@github.com>wrote:

> In fabfile.py:
>
> > +def configure():
> > +
> > +    # Daily cronjob for the producer
> > +    sudo("echo 'cd %s; %s/bin/python scraper.py producer' > /etc/cron.daily/scrapers" % (env.code_dir, env.env_dir))
> > +
> > +    supervisor_conf = open("deploy/consumers.conf").read() % { "code_dir" : env.code_dir, "env_dir" : env.env_dir }
> > +    sudo("echo '%s' > /etc/supervisor/conf.d/consumers.conf" % supervisor_conf)
> > +    sudo("supervisorctl update")
> > +
> > +
> > +def deploy():
> > +    with cd(env.code_dir):
> > +        run("git pull origin develop")
> > +
> > +    with virtualenv():
> > +        run('pip install -r requirements.txt')
>
> The fabfile looks great. The only change I would make is to install python
> packages as part of setup() rather than deploy(), but it's no train-smash
> either.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/Code4SA/various-scrapers/pull/5/files#r10557762>
> .
>



-- 
Adi Eyal
Data Specialist
phone: +27 78 014 2469
skype: adieyalcas
linkedin: http://za.linkedin.com/pub/dir/Adi/Eyal