Subdomain setup

From Dreamwidth Notes
Revision as of 15:09, 16 November 2015 by Kaberett (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

DNS Management

First, you will have to set up a wildcard subdomain record for your host. Different hosting providers have different interfaces, but here are some examples.

On Linode

Go to the DNS Manager section of your account and click on the domain zone your DW install is hosted on. Go to the "A/AAAA Records" section and note the IP address of the hosts:

Linode a records.png

(Note: the above picture already has the wildcard listed in it. Yours won't have that yet, but will when you finish this.) You will want to click on "Add a new A/AAAA Record":

Linode subdomain wildcard.png

Here, you will want to add * and the IP address you noted on the last page. Save this form and a wildcard subdomain should be added to your A/AAAA Records section.

Local development via dnsmasq

If you've set up a Dreamwidth development server on your local machine, you can use dnsmasq to give you a local DNS server with wildcard matching. Install it with

   apt-get install dnsmasq

The install should create the config directory /etc/dnsmasq.d/ -- text files in there will be picked up and added to dnsmasq's configuration.

Say you have a local webserver that you want to set up as avengers.mylocal. Create a file in dnsmasq's config directory (eg /etc/dnsmasq.d/avengers) with the following contents:


Now restart dnsmasq:

   /etc/init.d/dnsmasq restart

...and now anything ending in avengers.mylocal should resolve to avengers.mylocal, www.avengers.mylocal, thor.avengers.mylocal, www.loki.avengers.mylocal, ...


Note: This section is enabled by default (note current as of November 2015).

To configure your installation for user subdomains, uncomment the bolded lines in $LJHOME/etc/

# Support URLs of the form ?
# If so, what's the part after "username." ?
# If you ONLY want USER_VHOSTS to work and not the typical /users/USER and /community/USER
# then set this option:

If you only want certain user classes to have user subdomains, do not set $ONLY_USER_VHOSTS to 1, or journals who do not have this user capability won't work!

You will also have to set a user capability in etc/ called userdomain. If you want all users to have this capability, add it to %CAP_DEF:

%CAP_DEF = ( 
         'maxfriends' => 500,
         'userpics' => 1,
         'checkfriends_interval' => 60, 
         'checkfriends' => 1,
         'styles' => 0,
         'todomax' => 25, 
         'todosec' => 0,
         'friendsviewupdate' => 30, 
         'findsim' => 1,
         'getselfemail' => 0,
         'userdomain' => 1

Otherwise, you will have to add 'userdomain' => 1 to one or more of the user classes listed in %CAP.

You also need to add an entry to %SUBDOMAIN_FUNCTIONS (and create this hash if it does not already exist):

    'community' => 'journal',