Add new comment

Posted on by Steve - CC (not verified).

Hey Adam

This seems to be really close to what I need to learn.
I have a few Drupal sites that I've built for non-profits and modification and maintenance is much harder than it seems like it should be. I keep seeing clues that Drush and Git might be the way to go to make it easier and safer. I finally have the time to look into it more and found this article. I've been trying to get a handle on how they work and have been reading a ton but have a few holes in my understanding that I think you might be able to fill. Let me ask a few basic ones first:

With three servers - local, test and production - do I need to install Git on all of them or?

With three servers - local, test and production - do I need to install Drush on all of them or?

I'm thinking I'll use the same host that the production sites are at for the test site which will allow me to have an exact dupe of the production environment - any comments about the need for and method/s to create an exact dupe on the local environment?

TIA

Steve

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.