subdomain

I'm new to Nginx and I'm trying to get subdomains working. What I would like to do is take my domain (let's call it example.com ) and add: sub1.example.com , sub2.example.com , and also have www.example.com available. I know how to do this with Apache, but Nginx is being a real head scratcher. I'm running Debian 6. My current /etc/nginx/sites-enabled/example.com: server { server_name www.example.com example.com; access_log /srv/www/www.example.com/logs/access.log; error_log /srv/www/www.example.com/logs/error.log; root /srv/www/www.example.com/public_html; location / { index index.html index

I have a NAS/Server running at home 24/7 and run many different services on it. I have got a domain name pointing to it now, and was wondering if it would be possible to create sub-domains that point to different ports for different services. For example: http://subsonic.mydomain.com --> XXX.XXX.XXX.XXX:4040 http://minecraft.mydomain.com --> XXX.XXX.XXX.XXX:25565 http://files.mydomain.com --> XXX.XXX.XXX.XXX:4082 I have a single D-LINK router that currently port forwards all these ports to my NAS/Server whose IP is 192.168.0.104. EDIT: The server is running Ubuntu 12.04. What service or proxy

Using Morph Labs' Appspace to deploy a site means no automated way to redirect 'myapp.com' to 'www.myapp.com' (and no access to .htacess). Is there an in-rails way to do this? Would I need a plugin like subdomain-fu ? More specifically, I'm trying to do something like: 'myapp.com' => 'www.myapp.com' 'myapp.com/session/new' => 'www.myapp.com/session/new' Basically, I always want the 'www' subdomain prepended on every request (because the SSL cert specifically has a common name of 'www.myapp.com'). Maybe something like this would do the trick: class ApplicationController < ActionController::Base

I'm currently developing a security solution that should work across domains and as such I need a small private dns server to add various entries to. I could alter the hosts file to achieve the same result but since the hosts file doesn't support wildcard chars I will have a whole lot of entries, so a DNS server that supports wildcards would be a little bit easier. Any suggestions? As a reference: http://sourceforge.net/projects/acrylic/ Acrylic is a local DNS proxy which improves the performance of your computer by caching the responses coming from your DNS servers. I found it to work

There are two main strategies for handling multiple "applications" on the web: subdomains (e.g. wiki.example.org, blog.example.org, admin.example.org, api.example.org/v1) subdirs (e.g. example.org/wiki, example.org/blog, example.org/admin, example.org/api/v1) What are the differences (advantages and disadvantages) of these two solution when dealing with web programming (e.g. in terms of code organization, browsers security models, javascript etc). Edit: CW as there's a correct answer, but it's very broad. Besides the fact that from a security standpoint it is a bit easier to isolate an app

I'm starting a new web app project using Django and Pinax. I want to be able to give my users unique domain names like Wordpress and other sites do : username.wordpress.com . I'm not sure how to approach this with Django, since the url parsing logic (in urls.py) starts with the url AFTER the domain name. More specifically, there will be multiple groups of users, each group having a unique name. Not sure that makes a difference, but I thought I should mention that. Is there some way I can manipulate the http request so that the URL looks to Django as if the url were something like www.domain

I have searched and while I found lots of threads close, none were exactly what I am looking for... On my site, say example.com, I've created the subdomain secure.example.com This subdomain will have SSL. What I want to do is redirect requests to https://secure.example.com/path/ to www.example.com/path/ while keeping the url showing as https://secure.example.com/path/ note that the purpose of subdomain.example.com is for SSL so the redirect above will need to work with SSL I would like to use a few other redirects in the htaccess: 1) redirect non-www to www ignoring subdomains (so secure

I want to create sub-domains using PHP on the fly. Suppose a user registers himself as a name "ABC". Then I want to create a sub-domain named 'ABC.mydomain.com' automatically by PHP. I'm using a linux based server. Would anyone point me to the right direction? You should be aware that this is easily done using wildcard DNS records. This way: you do not have to register each user to your DNS server. your DNS A-record may contain as few as 1 record: e.g *.mydomain.com -> 12.34.56.78 your web server at 12.34.56.78 have to be configured to accept wildcard In your server-side scripts, you