VPS and the Bryghtbase SVN
Hello, I am currently planning out my support pathway for moving starter sites up and out of my VPS. I picture that I will have a full instance up and running all on it's own, and that I will then migrate it.
Now, the question is, when I was first setup on Bryght, I received a Drupal 5 install with it, and now I am ooking it all over wondering how I am going to make this work across instances.
I was thinking that what I would like most is for all the profiles and other information within this multi-instacne platform to be symlinked as much as possible.
perhaps a nice omnigraffle file would do the illustration trick, eh? ill work on that now. It's important to keep you guys in the loop on this because this is planning for scripting purposes, and I am trying hard to stay compatible with your SVN distro, know what I'm saying?
I have 2 clients that I will be moving to their own VPSs as soon as I bring them up from 4.7 to 5.0, and then more to follow.
Best practices, bring 'em on!
Comments
Nice thing about SVN, it's centralized
So, if you set up additional clients on new VPS, they will have the exact same centrally updated SVN tree on there. Ideally, you keep them all running on the same version, simply by issuing "svn update" commands.
Think as the SVN repo as a big symlink in the sky :P