Timeline for Suggestions for settings.php - Local dev, Development server, Live server
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2012 at 14:39 | comment | added | Charlie Schliesser | Agree with MikeyP completely. If the goal is to have as identical an environment as possible between dev, staging, and production then we wouldn't want to use the multisite method. | |
| Mar 3, 2011 at 18:06 | comment | added | Paul Jones |
@Mikey P: Using the method above means that everything is shared between the 2 sites. The only things that are different are the settings.php files, and both of those can be kept in version control.
|
|
| Mar 3, 2011 at 18:01 | comment | added | geerlingguy | @Mikey P - both solutions are valid—I think it's mostly up to personal/team preference here... there are tradeoffs with either approach, in my opinion. | |
| Mar 3, 2011 at 3:46 | comment | added | Mikey P | I think this is actually a poor way to handle dev and staging environments because they aren't actually different/separate sites, just different versions of the same site. In this case you would very much want to avoid having separate files for each site. I'd very much recommend using the method mentioned below where settings.php is versioned and settings specific to each site (DB settings) are put in a local.settings.php that is not versioned. | |
| Mar 2, 2011 at 21:16 | comment | added | geerlingguy | Accepting this answer - I'm going to try this on the site I'm currently working on. Looks like a good fit for my workflow. | |
| Mar 2, 2011 at 21:16 | vote | accept | geerlingguy | ||
| Sep 11, 2012 at 3:45 | |||||
| Mar 2, 2011 at 21:04 | comment | added | Paul Jones |
You could always try using symbolic links from the sites/dev.example.com/modules to sites/example.com/modules
|
|
| Mar 2, 2011 at 21:02 | comment | added | geerlingguy | That makes some sense, but I have a few sites where there are 5-10 multisite folders already, and having all the themes for those sites in sites/all/themes can be quite annoying. Not to mention my typical use of custom.module for each site. I guess I could use sitename_custom.module instead :-/ | |
| Mar 2, 2011 at 20:59 | history | answered | Paul Jones | CC BY-SA 2.5 |