Where is settings.php in drupal 7

If you scroll down a bit in the file, you will see a list of sample paths denoting the various directories Drupal will look for when trying to find the settings. In the end, Drupal doesn't find a directory it can relate the URL to, it will seek out the default directory.

Why does this matter? Well, for most installations, it doesn't. But one day you might want to install a new Drupal site but use the same code-base. That's when knowing this comes in handy. Also, if you are using Acquia Dev Desktop and you use its control panel to create multiple practice sites, the feature that creates the new sites for you is actually creating multiple site directories in sites.

As the comment suggests, assigning a base URL is optional but in the event you are having issues with your base URL being detected correctly by Drupal, this is one option for trying to rectify the issue.

Okay, now that we have URL's out of the way, scroll back up until you find the section on Database settings. As you know, Drupal relies on a database to store all the configuration information as well as your content.

When you download Drupal, you aren't downloading the database that goes with it. You are downloading code that will populate an empty database with all the tables Drupal needs. This means, when you manual install Drupal, you are expected to create an empty database that Drupal can use. Typically, all you need to know is the name of the database let's say you call it widget for your site widget. The process by which you create your database will vary depending on your hosting environment but someplace in the process, your empty database will need to be assigned to a user and given a password as well.

It's these three pieces of data you will need when completing the installation form Drupal presents in the browser. If Drupal is going to take care of updating the settings. As you can see there are other settings in the database array and if your environment expects something different, then you might need to make a change. BUT, the most common reason I can think of is when you migrate from your local installation to an installation on a live server. Imagine if you will, you've built your site using Acquia's Dev Destop and you the name of the database turns out to be a name you don't want to use on the live server.

The steps you would need to follow in migrating your site would be:. H ere's a detailed guide to changing the database connection in your settings. If you have a situation where you need multiple sites but instead of just sharing the code-base as we discussed earlier you need to share the database, the settings. The key to sharing one Drupal database with multiple sites is the prefix.

The prefix allows you to have multiple users tables, menus tables, etc. There are alot of tables in a Drupal database so before you decide this is the way to go, you should spend some time understanding what each table stores so that you can ensure all the tables that need to be unique from site to site are indeed that.

A mere 50 lines, as opposed to the original ! Much easier to read, and modify when needed. Not to mention that we're about to move 10 of them to a settings. You'll notice that there's still a commented-out section that's used to "Load local development override configuration, if available.

That file is were you might store the database credentials for each instance of your site, as well as configuration overrides that are specific to one instance of the site.

Let's set that up. Drupal 8. Note: example-dropscomposer the starting template for all Composer-managed sites on Pantheon includes this configuration in settings. Any site built from this example e. For Drupal 7 and earlier, Pantheon uses a variant of Pressflow Drupal to allow the server to automatically specify configuration settings, such as the database configuration without editing settings.

Permissions are handled automatically by Pantheon, so you can customize settings. The following articles include techniques and configurations for settings. You should never put the database connection information for a Pantheon database within your settings. These credentials will change. If you are having connection errors, make sure you are running Pressflow core.

This is a requirement. Use these configuration snippets to specify a local configuration that will be ignored by Pantheon, such as database credentials.

Configure environment-specific settings within the settings. Modifying the bundled settings. See Drush script: Quickstart. Drupal 8 will not run locally without a hash salt, but it need not be the same one set on the Pantheon platform; any sufficiently long random string will do.

Make sure to set one in settings. However, sites running on Pantheon are not vulnerable to this specific attack and the warning can be safely ignored.

If you would like to resolve the warning, use the following configuration:. Be sure to escape any characters that need to be escaped in regular expressions, including dots. If you're using the Drupal 8 redirects from our Configure Redirects doc, don't use this snippet as it conflicts. Yes, but only if at least one other file e.