gcollazo / fabulous Goto Github PK

Supervisor is not running at startup. You can configure an init.d script to do this.

sudo vi /etc/init.d/supervisord

Add the following:

# Supervisord auto-start
#
# description: Auto-starts supervisord
# processname: supervisord
# pidfile: /var/run/supervisord.pid

SUPERVISORD=/usr/local/bin/supervisord
SUPERVISORCTL=/usr/local/bin/supervisorctl

case $1 in
start)
        echo -n "Starting supervisord: "
        $SUPERVISORD
        echo
        ;;
stop)
        echo -n "Stopping supervisord: "
        $SUPERVISORCTL shutdown
        echo
        ;;
restart)
        echo -n "Stopping supervisord: "
        $SUPERVISORCTL shutdown
        echo
        echo -n "Starting supervisord: "
        $SUPERVISORD
        echo
        ;;
esac

And then...

sudo chmod +x /etc/init.d/supervisord

sudo update-rc.d supervisord defaults

sudo /etc/init.d/supervisord start

Obviously, this should probably go as added actions on cookbook.py and the init.d script as a template

Supervisor is not running at startup. You can configure an init.d script to do this.

sudo vi /etc/init.d/supervisord

Add the following:

SUPERVISORD=/usr/local/bin/supervisord
SUPERVISORCTL=/usr/local/bin/supervisorctl

case $1 in
start)
        echo -n "Starting supervisord: "
        $SUPERVISORD
        echo
        ;;
stop)
        echo -n "Stopping supervisord: "
        $SUPERVISORCTL shutdown
        echo
        ;;
restart)
        echo -n "Stopping supervisord: "
        $SUPERVISORCTL shutdown
        echo
        echo -n "Starting supervisord: "
        $SUPERVISORD
        echo
        ;;
esac

And then...

sudo chmod +x /etc/init.d/supervisord
sudo update-rc.d supervisord defaults
sudo /etc/init.d/supervisord start

Obviously, this should probably go as added actions on cookbook.py and the init.d script as a template

The command 'sudo /etc/init.d/supervisord start', which is the last commend executed as part of the cookbook, causes this error to output:

[ec2-xxxx.compute-1.amazonaws.com] sudo: /etc/init.d/supervisord start
[ec2-xxxx.compute-1.amazonaws.com] out: Starting supervisord: Error: Another program is already listening on a port that one of our HTTP servers is configured to use. Shut this program down first befor[ec2-75-101-218-250.compute-1.amazonaws.com] out:
[ec2-xxxx.compute-1.amazonaws.com] out: For help, use /usr/local/bin/supervisord -h
[ec2-xxxx.compute-1.amazonaws.com] out:
[ec2-xxxx.compute-1.amazonaws.com] out:

Running the command on the remote server after deployment has finished produces the same error message.

The supervisord daemon runs without a hitch & performs as expected, though.

Why it shows Error 404

Perhaps I'm missing something, but it looks like GITHUB_REPO is never referenced, and no github app is ever deployed.

Hello there,

The idea of this project is amazing! I'm quite new to django deployment and I could not find any good resource to start setting up my own server.

I'm using Django 1.7.1 with Python 3.2. All good tutorials are still pointing to Django 1.6 and Python 2.

Do you know what is necessary to change in this project in order to create proper up-to-date server instances?

Thanks a lot!

The file '/etc/supervisord.conf' contains the following section for managing the Django/gunicorn app:

[program:polls]
command=/home/ubuntu/.virtualenvs/polls/bin/gunicorn_django -c gunicorn.conf.py settings.py
directory=/home/ubuntu/webapps/polls
user=root
autostart=true
autorestart=true
redirect_stderr=true

This implies that the gunicorn processes execute as root, which is easily verified using 'top'.

This is incredibly dangerous. Is there some reason why it doesn't execute as 'www-data' or some other user?

It says:

$ fab ulous

Don't you need to say

$ python fabulous.py

or something like that?

I get "The program 'fab' is not currently installed".