managing many server names

[W. Andrew Loe III]

Why not just have it listen on an IP and point your domain that
everyone is CNAMING to at that IP?

On Mon, Nov 16, 2009 at 9:17 PM, guynaor <guynaor at g2ix.com> wrote:
> Hi,
>
> Just include it from a file. I have a site an nginx install with around
> 16K names in one of the server entries, and aside from increasing the size
> of the hash table / buckets it all worked with no issues.
>
> Bye,
>
> Guy.
>
>
> On Mon, 16 Nov 2009 23:48:49 -0500, Patrick Aljord <patcito at gmail.com>
> wrote:
>> Hi,
>>
>> I have my site config that looks like this:
>>
>> server {
>>         listen   80;
>>         server_name  www.foo.com *.foo.com  foo.bar.net example.com
>> allnginx.com foobar.com barfoo.com xyz.com yzt.net;
>>         access_log  /var/log/nginx/foo.access.log;
>>         root /home/app/foo/current/public;
>> }
>>
>> I allow my clients to use a cname for their domains, the problem is
>> that my site config is going to get huge because of all the
>> server_name values. Is there a way to move them to another file in a
>> var that I would include in the site config? Or maybe a more elegant
>> solution?
>>
>> Thanks in advance,
>>
>> Pat
>
>