By mwu on

I've set up a bunch of different sandboxes to test modules. (By a sand box, I just mean a test site. I don't know if I'm using the word sandbox correctly.)

I've started setting up a test site for each complex module I'm testing, so that I know any problems is not due to interaction.

I know have 5:
--one to test cck
--one to test the lm_paypal suite
--one to test cck plus lm_paypal suite
--one to test everything else together
--(one to be the live site but is not live yet)

I'm starting to lose track of which site has which modules, settings, content types, content, etc. etc. also, it's a pain to make the many content types multiple times. I imagine some of you have worked out the most efficient way to test modules and manage test sites. Your suggestions and descriptions of what you do would be appreciated.

⋅ Categories: Drupal 4.7.x

Comments

vm’s picture

vm commented

#1 I have two, one for testing brandnew modules.
#2 one (which is constantly backed up) that has all modules that are known working and compatible with each other.

if a module works as expected in #1 i move it to #2 if all is still well, I move it to live environment.

working with backups is easier then working with 5 sandboxes.

LeeMcL’s picture

LeeMcL commented

I have a pretty similar setup. To help me keep track of which is which I have a different theme for each site as a visual clue as to which I'm on now. You could also set the site title or slogan to list its purpose too.
--
Lee McLoughlin
lmmrtech.com

mwu’s picture

mwu commented

Lee,
that's an excellent idea. I think I'll put the names of the (major) installed modules into the site slogan, that way I can see at a glance which modules are installed.

do you mean your site up is similar to mine or the other persons?