otty / dotfiles

All tools/Sqitch

Sqitch

sqitch

Sensible database-native change management for framework-free development and dependable deployment.

Detected by sqitch | macOS, Linux, Windows |sqitch.org

Sync it sqitch.toml

Sync rules

What travels, what stays, what never leaves

Sqitch in your home directory Every rule on this page, by file

…

name = Octo Cat

email = octocat@example.com

[engine "pg"]

client = /opt/homebrew/opt/libpq/bin/psqlmachine-local

registry = sqitch

target = flipr_test

uri = db:pg://sqitch:FAKEpassword0000@localhost/flipr_test

[engine "sqlite"]

client = /usr/local/bin/sqlite3machine-local

[target "flipr_test"]

uri = db:pg://sqitch:FAKEpassword0000@localhost/flipr_test

[target "flipr_prod"]

uri = db:pg://deploy:FAKEpassword1111@db.example.com:5432/flipr

registry = sqitch

[core "vcs"]

client = /opt/homebrew/bin/gitmachine-local

[deploy]

verify = true

Each machine keeps its own copy of these.

uri

Lifted into your secret store; the rest of the file syncs.

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/sqitch.tomlThe file this page is generated from

id = "sqitch"

name = "Sqitch"

homepage = "https://sqitch.org"

description = "Sensible database-native change management for framework-free development and dependable deployment."

# The project's own logo, the apple-touch-icon on sqitch.org.

icon = "https://sqitch.org/img/apple-touch.png"

detect = ["sqitch"]

# The description is sqitch.org's own summary line.

# sqitch-config(3), FILES: "~/.sqitch/sqitch.conf" is "used to store a per-user

# configuration as fallback values for the ./sqitch.conf file", overridable

# with $SQITCH_USER_CONFIG. The system file, $(prefix)/etc/sqitch/sqitch.conf,

# is not user-level; ./sqitch.conf belongs to the project's repository, not to

# the user's home.

paths = ["~/.sqitch/sqitch.conf"]

exclude = []

# The user config is a git-style ini file: user.name / user.email, editor and

# pager preferences, engine defaults. It is not a credential end to end — only

# the connection URI in it can be, and that is lifted out below.

secret = []

# Read once per invocation; sqitch is a client with no resident process.

side_effect = false

# sqitch-target(3) gives the URI format as

# "db:engine:[//[user[:password]@][host][:port]/][dbname][?params][#fragment]",

# so a `uri` line can carry a database password in the clear — which is why

# sqitch-authentication(3) opens with "Don't use Passwords" and offers a

# password file and $SQITCH_PASSWORD instead. The key is written `uri` inside a

# [target "name"] or [engine "pg"] section, which is the shape a prefix match

# sees. Lifting the whole line is deliberate over-classification: a URI without

# a password costs the user one setting, a URI with one costs them the

# password.

[[secret_paths]]

file = "~/.sqitch/sqitch.conf"

match = { prefix = ["uri"] }

# sqitch-config(3): "engine.$engine.client — Path to the engine command-line

# client. Defaults to the first instance found in the path", and "core.vcs.client"

# the same for the VCS client. Both are absolute paths to a binary on this

# host's disk; the next machine has psql or git somewhere else. It is a path

# decided by the kind of machine — a Homebrew prefix, a distribution layout —

# rather than by the individual box, so it travels to another machine of the

# same class.

[[machine_lines]]

file = "~/.sqitch/sqitch.conf"

match = { prefix = ["client"] }

scope = "platform"

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/sqitch. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page. None of them splits client for you — that part is Otty’s own sync, or a template you write by hand.