Custom Query (21 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 21)

1 2 3 4 5 6 7
Ticket Resolution Summary Owner Reporter
#13 fixed Couchdb-dump/load error handling does not use STDERR Lucas Bonnet Vincent Caron
Description

source:/couchdb/couch-dump and source:/couchdb/couch-load should use print STDERR for error messages, or preferrably die().

#14 fixed Use LWP instead of wget Lucas Bonnet Vincent Caron
Description

Invocations of wget are not really Perlish, LWP has been around for so long that it's ubiquitous. And it should be faster too, especially if the same UA can be reused for all requests since they look all targeted to the same host.

And the current wget invocation fails on quoting spaces and shell metacharacaters:

`wget -q $doc_url -O design_$1`;

Should be at least:

system('wget', '-q', $doc_url, '-O', "design_$1");

Or better:

Use LWP::Simple;
$LWP::Simple::ua->agent('couchdb-dump/0.3');

# Later...
my $http_status = getstore($doc_url, "design_$1");
#23 fixed Use nginx as single dispatcher for ror-farm vservers Lucas Bonnet Vincent Caron
Description

Our production setup based on the source:/ror-farm software currently uses:

  • haproxy as a first stage dispatcher (vhost based, HTTP only), selecting the proper physical server
  • lighttpd as a second stage dispatcher (vost based, could do HTTPS but unused) selecting the proper local vserver

Haproxy can't do HTTPS, so we would like some SSL enabled reverse proxy. Lighttpd is bugging us, so we would like something else.

The specialized options like 'pen' (barely maintained for 2 years) and 'varnish' (mostly a sophisticated cache - we're not looking into caches) do not appeal to me.

Nginx looks good: it's known to be very good at reverse proxying (it as been designed for this goal first), and can be configured as a full blown HTTP server if needed.

I propose to write a 'ror-build-nginx' which creates a simpe conf which:

  • forwards HTTP _and_ HTTPS requests to the local vserver if a vhost match
  • forwards to the next cloud server otherwise

It should work as is with two physical servers.

It will need a global configuration for ror-farm instances starting from 3 servers, at least to map instances to physical servers from a single lookup. We'll have to do this at some point anyway...

PS: this is motivated by the fact that I need HTTPS *now* and more than 3 servers maybe real soon (py*thing*).

Pro ? Con ?

1 2 3 4 5 6 7
Note: See TracQuery for help on using queries.