Using Variable in fastcgi_pass

Hey,

I am trying to use a variable in the fastcgi_pass directive. It does not
get parsed however.

Example:
2008/10/20 12:09:59 [crit] 4475#0: *3 connect() to
unix:/var/run/php-fpm/socket/$userid failed (2: No such file or
directory) while connecting to upstream, client: 127.0.0.1, server:
localhost, request: “GET /info.php HTTP/1.1”, upstream:
“fastcgi://unix:/var/run/php-fpm/socket/$userid:”, host:
345232.user.domain.net

Is this not supported? It would be a really important feature to me,
since it would enable me to not have to reload nginx periodically with a
new config file!

Regards,
Samy

Maybe it would be helpful if I included my config file:
server {
listen 127.0.0.1:81;
server_name localhost;

    set $userid "default";

    if ($host ~ "^(.+)\.user\.domain\.net$") {
            set $userid $1;
    }

    root   /www/$userid;
    index  index.html index.htm;

    location ~ \.php$ {
            fastcgi_pass   unix:/var/run/php-fpm/socket/$userid;
    }

}

Samuel Vogel schrieb:

On Mon, Oct 20, 2008 at 02:16:18PM +0200, Samuel Vogel wrote:

Is this not supported? It would be a really important feature to me,
since it would enable me to not have to reload nginx periodically with a
new config file!

No, variables are not supoorted in fastcgi_pass currently.
I will probably add them in the near future.

Igor S. schrieb:

No, variables are not supoorted in fastcgi_pass currently.
I will probably add them in the near future.

This would be a really important feature to us. I would guess that it
wouldn’t be too hard to implement, since other directives already
support variables.
Is there any way to get you to implement this for the next release of
nginx?

Regards,
Samy

Igor S. schrieb:

No, variables are not supoorted in fastcgi_pass currently.
I will probably add them in the near future.

Is there any timeframe when you will get to add this feature?
It would be really helpful for my in the environment I have to set up
currently!

Regards,
Samy

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs