pirateradio / proximo-stacklet

Send outbound traffic from a process through a Proximo proxy
http://addons.heroku.com/proximo
12 stars 4 forks source link

Default instructions fail on OSX #1

Open roughcut opened 11 years ago

roughcut commented 11 years ago

Following the instructions here (https://devcenter.heroku.com//articles/proximo#determining-your-static-ip-address) with Rails 3.2.9, Ruby 1.9.3 on OSX yields the following:

india:roughcut (dev) dr jm$ foreman start
10:31:31 web.1  | started with pid 80093
10:31:31 web.1  | You must first install Proximo:
10:31:31 web.1  | heroku addons:add proximo:development
10:31:31 web.1  | readlink: illegal option -- f
10:31:31 web.1  | usage: readlink [-n] [file ...]
10:31:31 web.1  | usage: dirname path
10:31:31 web.1  | usage: dirname path
10:31:31 web.1  | Proxying traffic bound for 0.0.0.0/0 via Proximo host :1080
10:31:31 web.1  | /Users/pivotal/workspace/roughcut/bin/proximo: line 35: /vendor/dante/socks.conf: No such file or directory
10:31:31 web.1  | cat: /vendor/dante/socks.conf.template: No such file or directory
10:31:31 web.1  | chmod: /vendor/dante/bin/*: No such file or directory
10:31:31 web.1  | /Users/pivotal/workspace/roughcut/bin/proximo: line 42: /vendor/dante/bin/socksify: No such file or directory
10:31:31 web.1  | /Users/pivotal/workspace/roughcut/bin/proximo: line 42: exec: /vendor/dante/bin/socksify: cannot execute: No such file or directory
10:31:31 web.1  | exited with code 126
10:31:31 system | sending SIGTERM to all processes
SIGTERM received

This is because readlink -f $0 is not a valid command on OSX and the installed bin/proximo is not a soft link but rather an executable, so readlink bin/proximo would return nothing anyways (when assigning a value to $DANTE_DIR) -- so dante/socks.conf is not found.

The initial error "You must first install Promixo" is because the PROXIMO_URL environment variable is not being set by Heroku for some reason. Manually specifying it gets us past this error but not the readlink error(s).

Thanks!

roughcut commented 11 years ago

We had to perform the following steps to get proximo working:

  1. Removing readlink -f from bin/proximo shell script
  2. Add the environment variable PROXIMO_URL locally on our development box.
chuckg commented 11 years ago

+1, I can confirm this issue.

sainejob commented 10 years ago

+1, confirmed again