Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



28 Commits

Repository files navigation

Sequel Pro for Chassis

Adds a handy vagrant sequel command to simplify access to your database.

Supported database clients include:

  • Sequel Pro Note: The test build doesn't crash regularly
  • Sequel Ace
  • Any client that supports .spf files


We recommend installing this extension globally to make it available on every Chassis box.

git clone ~/.chassis/extensions/sequelpro

Alternatively to install this extension into a single Chassis box, add chassis/sequelpro to your extensions list in your config.local.yaml:

  - chassis/sequelpro

(For manual installation in an individual Chassis box, clone this repository into that Chassis box's extensions directory.)


Once the virtual machine is running, run vagrant sequel within the Chassis folder to open the VM's database in your client.


This extension allows for custom configuration options which can be added in one of your configuration files. Here's an example configuration:

# MySQL database details.
  name: your_database
  user: your_username
  password: your_password
  prefix: bq_

The connection to your MySQL database is made by tunnelling over the same SSH connection used for vagrant ssh, so no networking configuration is necessary.

Connection Errors

If you get a connection error, the first thing to attempt to debug is to check the details that your client gives you.

The connection error message can be very long and in Sequel Pro and Sequel Ace it may get truncated. You can click within the error message and press cmd+a then cmd+c to copy the full text.

key_load_public: No such file or directory

If you get this error on macOS Sierra, it's possible that you have too many SSH keys loaded into your ssh-agent. If you're using multiple Chassis boxes with this setup in your SSH config (AddKeysToAgent yes), each new box you add will be added to your agent. With too many of these, SSH will hit the authentication retries limit before getting to the correct key.

The simple solution is to add this to your ~/.ssh/config file:

# Disable checks on Vagrant machines
	# Skip adding to agent
	AddKeysToAgent no

	# Only use key specified on CLI
	IdentitiesOnly yes

	# Skip known hosts
	UserKnownHostsFile /dev/null
	StrictHostKeyChecking no

This disables using system-level keys (both from the agent, and your regular SSH keys), and disables host checks (which are not necessary for localhost). This does not affect vagrant ssh, which already uses these options.


No releases published


No packages published

Contributors 4