Geek Answers Handbook

Drupal and version control

I was looking for similar questions for myself, and one seemed promising, but the accepted anser is not applicable to me (I think.)

Drupal Versioning Strategy?

Basically, you need to have rights on the server on which you are deploying. This is not my situation. I am using a hosting service and I don’t think I can install SVN on it.

So, I just develop on the "dummy" site and somehow do a lot of juggling, testing the ont eh dummy site, getting the content (including the database) and putting it in SVN, and then sending it to my live site

What does the Drupal database look like? My dummy and live sites will not / will not have the same login / logout, etc.

What are others doing for Drupal development and version control?

+5
source share
2 answers

Just a few hosting services - even cheap shared hosts - have an SVN or CVS client installed. This is different from SVN hosting, a service that some hosting companies clearly offer. It is worth checking out; with a version control client, your life will be much easier, no matter what.

Our startup workflow tends to go something like this:

  • Codebase setup
  • Put it in SVN / git / regardless of development, code, content creation, configuration, etc.
  • Take DB pictures at regular intervals to keep common sense.
  • Delete any dummy content or dummy user accounts created during development
  • Enter the code in the field for production or testing.
    • , .
    • , , , .
    • . "" /. - .
  • , /db -, , SFT adhoc. , , , , , -.

; . -

+4

Drupal.

1/

GIT - , Drupal, .

Drupal .

  • . , , . , , , , UUID UUID, ..


  • Drush , Drupal. , Drush , .

2/

, , .

Drupal GIT, , GIT - .

, , , , , !

0

More articles:


All Articles