Mixed Virtualhosts and IP hosts

[Scott Larson]

      I did that example off the top of my head, but yes I do have  
create_full_put_path enabled, it was more an example of using location  
to enable the use of multiple devices in a config.  The  
client_body_temp_path is important if each location is at a separate  
physical mount point otherwise you'll run into nginx not writing data.
-- 
Scott Larson
Network Administrator

Wiredrive
4216 3/4 Glencoe Ave
Marina Del Rey, CA 90292
t 310.823.8238
stl at wiredrive.com
http://www.wiredrive.com

On Aug 31, 2008, at 1:18 AM, mike wrote:

> i only have one device on those servers.
>
> however, i do have
>
>        location /dev4 {
>            root /var/mogdata/;
>            client_body_temp_path /var/mogdata/dev4/.tmp;
>            dav_methods put delete mkcol copy move;
>            dav_access user:rw group:rw all:r;
>            # not sure if this is needed
>            create_full_put_path on;
>        }
>        location /dev5 {
>            root /var/mogdata/;
>            client_body_temp_path /var/mogdata/dev5/.tmp;
>            dav_methods put delete mkcol copy move;
>            dav_access user:rw group:rw all:r;
>            # not sure if this is needed
>            create_full_put_path on;
>        }
>
> on a server that does have two devices.
>
> and i guess i answered a previous question - you could use a different
> client_body_temp_path. funny how i already figured that out in the
> last and forgot it :) (igor already told me a second time, but
> apparently i had it figured out on my own)
>
> so according to your config you don't have the "create_full_put_path"
> and it still works like a charm? i am not using mine in production
> yet, i assume you are...
>
>
> On 8/31/08, Scott Larson <stl at wiredrive.com> wrote:
>>    That's basically what I've done with the nginx config for  
>> mogilefs, only
>> a little different:
>>
>> http {
>>    ...
>>   server {
>>       listen       7500;
>>       server_name  localhost;
>>
>>       charset utf-8;
>>
>>       location /dev1 {
>>           root   /var/mogdata;
>>           client_body_temp_path /var/mogdata/dev1;
>>           dav_methods put delete mkcol copy move;
>>           dav_access user:rw group:rw all:r;
>>       }
>>
>>       location /dev2 {
>>           root   /var/mogdata;
>>           client_body_temp_path /var/mogdata/dev2;
>>           dav_methods put delete mkcol copy move;
>>           dav_access user:rw group:rw all:r;
>>       }
>>    }
>> }
>>
>>    Each /dev is actually a dedicated disk with the same name.   
>> Doing it
>> that way lets you load up a box or add disks at will.  Not to go  
>> way off
>> topic on mogilefs.
>>
>> --
>> Scott Larson
>> Network Administrator
>>
>> Wiredrive
>> 4216 3/4 Glencoe Ave
>> Marina Del Rey, CA 90292
>> t 310.823.8238
>> stl at wiredrive.com
>> http://www.wiredrive.com
>>
>>
>> On Aug 31, 2008, at 12:37 AM, mike wrote:
>>
>>> seems to work well - just took out that second http {} block and put
>>> it in the first one and it seems to be functional still for  
>>> mogilefs.
>>>
>>> cool!
>>>
>>> On 8/31/08, Igor Sysoev <is at rambler-co.ru> wrote:
>>>
>>>> On Sun, Aug 31, 2008 at 12:30:14AM -0700, mike wrote:
>>>>
>>>>
>>>>> I am totally fine with just making an additional server {} block
>>>>> instead of http {}
>>>>>
>>>>> This is pretty much the only configuration option I'd want to  
>>>>> change:
>>>>> client_body_temp_path /var/mogdata/.tmp;
>>>>>
>>>>> would this work? I guess the more I think about it I don't care  
>>>>> where
>>>>> it puts the temp files... I just know that /var/mogdata/.tmp works
>>>>> nicely for the mogilefs stuff.
>>>>>
>>>>>
>>>>>         server {
>>>>>                    access_log off;
>>>>>                    listen 7500;
>>>>>                    server_name localhost;
>>>>>                    client_body_temp_path /var/mogdata/.tmp;
>>>>>                    charset utf-8;
>>>>>                    location / {
>>>>>                            root /var/mogdata/;
>>>>>                            dav_methods put delete mkcol copy move;
>>>>>                            dav_access user:rw group:rw all:r;
>>>>>                            create_full_put_path on;
>>>>>                    }
>>>>>         }
>>>>>
>>>>
>>>> Yes, you may set/override client_body_temp_path on http/server/ 
>>>> locaiton
>> level.
>>>>
>>>>
>>>> --
>>>> Igor Sysoev
>>>> http://sysoev.ru/en/
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>