Changes between Version 3 and Version 4 of setup_dedicated_ip


Ignore:
Timestamp:
Oct 14, 2007, 5:34:44 PM (12 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • setup_dedicated_ip

    v3 v4  
    11If a member wants a dedicated IP on one of our shared servers, these are the steps for setting it up.
    22
    3  * Allocated the IP by editing the [wiki:ip_allocation] page, putting the member domain name next to the next available IP address.
    4 
    5  * Edit the file /etc/network/interfaces on the machine in which the account is hosted. Add a stanza like the following:
    6 
     3 1. Allocated the IP by editing the [wiki:ip_allocation] page, putting the member domain name next to the next available IP address.
     4 1. Edit the file /etc/network/interfaces on the machine in which the account is hosted. Add a stanza like the following:
    75{{{
    86auto eth0:summup.org
     
    119  netmask 255.255.255.240
    1210}}}
    13 
    1411summup.org is the domain name of hosting order. The Address and netmask should reflect the address and netmask of the record you took from the [wiki:ip_allocation IP allocation] page.
    15 
    16  * Bring the new IP up with:
    17 
     12 1. Bring the new IP up with:
    1813{{{
    1914sudo ifup eth0:summup.org
    2015}}}
    21 
    2216Change summup.org to the domain name that you used.
    23 
    24  * Modify the DNS records via red. For advanced users, you should ask them to make this change. Change the IP address of the A records to the new ip (usually this would just be, in the example above, summup.org and www.summup.org). The SSL certificate will typically only apply to these domains - so you don't want to change the IP address of, for example, summup.mayfirst.org.
    25 
    26  * Add an ssl record to the web config. For advanced users, you should ask them to make this change. Under web config, click add new item. Be sure to copy and paste the values from the existing web config rather than taking the default values - you want to be sure to include any extras that you might have added (like the drupal !AllowOverride lines). Specify the same login as the owner, make it enabled, specify https, for IP address specify the IP address that has been allocated. Finally, add three new lines:
    27 
     17 1. Modify the DNS records via red. For advanced users, you should ask them to make this change. Change the IP address of the A records to the new ip (usually this would just be, in the example above, summup.org and www.summup.org). The SSL certificate will typically only apply to these domains - so you don't want to change the IP address of, for example, summup.mayfirst.org.
     18 1. Add an ssl record to the web config. For advanced users, you should ask them to make this change. Under web config, click add new item. Be sure to copy and paste the values from the existing web config rather than taking the default values - you want to be sure to include any extras that you might have added (like the drupal !AllowOverride lines). Specify the same login as the owner, make it enabled, specify https, for IP address specify the IP address that has been allocated. Finally, add three new lines:
    2819{{{
    2920#SSL Stuff
     
    3223SSLCertificateKeyFile /etc/apache2/ssl/chavez.mayfirst.org.key
    3324}}}
    34 
    3525Replace chavez with the name of the server the site is hosted on. NOTE: They will need to change these lines after they have purchased an SSL certificate so that they point to their own ssl certificate. These lines are just starters so that it works without an error.