![]() If your hosting company won't allow you SSH access: you can accomplish the previous step by uploading a specially configured text file see here for instructions.Here, is the name of the directory you deleted in the previous step. SSH into your site, and type this (filling in the correct information, of course): ln -s /home//public_html/ /home//public_html/.Delete the directory in public_html that was created when you added the new domain or subdomain.Also create a directory in public_html/sites/ named files. Upload the modified settings.php to the directory for your new site (public_html/sites/).Whatever is in the settings.php for your original Drupal site, don't change it for the second site.) (Note: your hosting company might require something other than "localhost" there. If your new database has the same user as your original Drupal database, the only thing you have to change is the at the end of the line. 'username' => ‘ username_with_access_to_database', If there are other differences between the configuration in your file and this example below, use the settings in your file: Make a copy of the settings.php file for your main Drupal install (it should be in public_html/sites/default) and modify the things in bold, in order to put in the new database, username and password.FTP to your site (or SSH, if you prefer and your hosting company permits it) and create in public_html/sites a new directory with the full name of your new site:.(Do NOT try to circumvent the symlink step by creating the document root for your subdomain in sites/. ): in cPanel, go to Subdomains, add your subdomain, and for Document Root, create a directory directly in in public_html. ![]() This will create a directory in public_html/mysecondproject. ): log into cPanel, go into Domain Manager and add a domain as an addon (NOT parked). If you're using a new domain name for your second site (e.g.Create a user (or use the same user you assigned to your main Drupal install) who has full permissions to the database. Create a database for the second site, the same way you did for your main Drupal install.If your main Drupal install is in another directory, modify the directions accordingly- for instance, where it says "public_html/sites", instead go to "public_html//sites": when you open the public_html directory, you see folders like "sites", "modules", "profiles" and files like "install.php" and "index.php"). This assumes that your main Drupal install is directly in the public_html directory (i.e. Now for the specific steps for how to make this work. Now when you go to, the server looks for the folder it created for the new site, the symlink redirects it to the to the main Drupal directory you set up for your first site, then the sites/sites.php file directs it to the folder that corresponds to your second project’s files.In your Drupal sitesfolder, create a directory for your new domain.the one you’ve already set up for your first site). ![]() You need to remove that directory and create a symlink (like a fake directory that redirects to a real directory somewhere else) in its place that points to the main Drupal install (i.e.When you go to, the server looks in that /home//public_html/newdomain directory for what it should display. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |