Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Tutorial Improvements: recommend how to get started with existing databases that aren't using sqitch #77

Closed
joevandyk opened this Issue · 4 comments

2 participants

@joevandyk

I'm guessing this is will be the case for most people coming to sqitch.

The existing schema should be known to sqitch, so that sqitch can bootstrap new development databases with the same structure. But when sqitch deploys to existing production databases, sqitch shouldn't try to deploy the already existing schema.

@joevandyk

Possibly this should be done with a 'bootstrap' command, so that sqitch doesn't try to deploy the initial schema to databases that don't already have sqitch installed?

@theory
Owner

That's what the --log-only option to sqitch deploy is for. For bootstrapping existing projects, there's issue #24.

@theory theory closed this
@joevandyk

Ah, yes, the --log-only command would be helpful. Maybe add that to a Getting Started doc?

Steps:

  • Install sqitch, setup sqitch directory
  • Dump initial schema, make a new deployment file
  • Check in, tag as v1.
  • Your first deployment needs to be a --log-only deployment to v1 to existing databases. Then you can deploy as normal.

Does that sound right?

@theory
Owner

Yes.

Might want to start an FAQ, I dunno…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.