otty / dotfiles

All tools/Sequel Pro

Sequel Pro

sequel-pro

MySQL/MariaDB database management for macOS

Detected by com.sequelpro.SequelPro | macOS |www.sequelpro.com

Sync it sequel-pro.toml

Sync rules

What travels, what stays, what never leaves

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

· ~/Library/Application Support/Sequel Pro/ Sync

· ~/Library/Preferences/com.sequelpro.SequelPro.plist Sync

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

apps/sequel-pro.tomlThe file this page is generated from

id = "sequel-pro"

name = "Sequel Pro"

homepage = "https://www.sequelpro.com/"

# The project's own repository description.

description = "MySQL/MariaDB database management for macOS"

# The app icon, from the project's GitHub organisation avatar — sequelpro.com

# no longer answers.

icon = "https://github.com/sequelpro.png"

# Sequel Pro ships no command-line tool, so `detect` carries the bundle

# identifier. It is the literal string in the app's own

# Resources/Plists/Info.plist (CFBundleIdentifier = com.sequelpro.SequelPro),

# and the Homebrew cask zaps the matching preferences domain

# (Casks/s/sequel-pro.rb).

detect = ["com.sequelpro.SequelPro"]

platforms = ["macos"]

# Development stopped — the cask has been `disable!`d since 2024-12-16 with

# replacement_cask "sequel-ace" — but the app still runs and its files are

# where it left them, which is exactly when a user needs to know what to carry.

# Two locations, both under the user's home:

# ~/Library/Application Support/Sequel Pro/ is the app's own directory. Its

# source names the three subfolders it creates there: SPConstants.m has

# SPDataSupportFolder = "Data", SPThemesSupportFolder = "Themes" and

# SPBundleSupportFolder = "Bundles", and SPFavoritesController.m documents the

# first one exactly — "Attempts to load the users connection favorites from

# ~/Library/Application Support/Sequel Pro/Data/Favorites.plist". Themes and

# Bundles are the user's own editor themes and command bundles;

# SPEditorPreferencePane.m writes the themes into that Themes folder with the

# extension SPConstants.m calls SPColorThemeFileExtension = "spTheme".

# ~/Library/Preferences/com.sequelpro.SequelPro.plist is the preferences

# domain, named in the same cask's zap stanza.

# [appData] and [preferences] are ~/Library/Application Support and

# ~/Library/Preferences; the entry is macOS-only, so there is no other platform

# for those roots to stand for.

paths = [

"[appData]/Sequel Pro/",

"[preferences]/com.sequelpro.SequelPro.plist",

]

# The cask's zap list keeps the rest elsewhere — ~/Library/Caches/

# com.sequelpro.SequelPro and ~/Library/Saved Application State/

# com.sequelpro.SequelPro.savedState — neither of them below a path above, so

# nothing needs carving out.

exclude = []

# Not a credential store: Favorites.plist holds each connection's name, host,

# user, database and SSH tunnel settings, while the passwords go to the macOS

# Keychain through the app's own Source/SPKeychain.m. Nothing under the two

# locations above is a credential end to end.

secret = []

# No machine_lines: the favorites, themes and bundles are the whole reason to

# carry these files, and a property list has no matcher in this schema anyway —

# `format` covers toml, yaml and json only.

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/sequel-pro. 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.