1. Mikhail Korobov
  2. django-fab-deploy
  3. Issues
Issue #28 open

apache port binding doesn't work on Ubuntu-10.04

Mikhail Korobov
repo owner created an issue

No description provided.

Comments (4)

  1. Michael Brown

    Hi I've just experienced an issue similar to this on a machine with a customised .profile The effect can rewrite the ports file (removing any other vhosts) so it's quite serious. Note the first list item is a bleed message.

    Perhaps "cat <PORTS_FILE> should be replaced with an "scp <PORTS_FILE> to /tmp/"

    ipdb> l
        115     import ipdb; ipdb.set_trace()
        116 
        117     lines = _ports_lines()
        118 
        119     # take over ports.conf
    --> 120     TAKEOVER_STRING = '# This file is managed by django-fab-deploy. Please do not edit it manually.'
        121     if lines[0] != TAKEOVER_STRING:
        122         lines = [TAKEOVER_STRING]
        123 
        124     used_ports = _used_ports(lines)
        125 
    
    ipdb> lines
    ['sudo: unable to resolve host linode2', '# This file is managed by django-fab-deploy. Please do not edit it manually.', '', ..... 
    ipdb> 
    Stopped.
    
  2. Mikhail Korobov reporter

    Hello,

    This issue is really serious, thanks for tracking it down!

    Port management was overhauled in the development version of django-fab-deploy and the port management code no longer has this issue, but the released django-fab-deploy version should be fixed and there may be similar issues with "cat" usage over the codebase. I'll check this.

    "cat <PORTS_FILE>" must be replaced with fabric.operations.get()

  3. Log in to comment