Skip to main content
Point TablePro at a project folder and it reads the database settings the project already has, so you do not have to copy them out of a .env file by hand.

​
Open a folder

  • File > Open Project Folder…
  • Add from Existing > Open Project Folder… on the welcome screen
Pick the folder in the panel that appears. TablePro scans it and lists what it found.

​
Pick a connection

Each row shows the database type, host, port, user, and database, plus the file and key it came from. Select one and click Continue. The connection form opens filled in, and nothing is saved or connected until you review it and click Save. Passwords are never shown. A row says Password found when the file has one, and the value goes straight to your Keychain when you save. Rows can carry extra notes: A connection starts at the Alert Safe Mode level instead of Silent when prod, production, or live shows up as a whole word in the file path, the host, or the database name.

​
Files it reads

Template files are skipped, so .env.example, .env.sample, .env.template, and .env.dist never appear. .envrc is a shell script, so TablePro never reads or runs it. The scan does not follow symlinks, skips node_modules, .git, vendor, dist, build and similar directories, goes four levels deep, and ignores files over 1 MB. It reads only the folder you picked, with one exception: WordPress allows wp-config.php to sit one level above the site, so that single file is checked in the parent folder too. When it comes from there, the row shows the path as ../wp-config.php.

​
When a value cannot be read

Some settings point somewhere else instead of holding a value, like ${{Postgres.DATABASE_URL}} on Railway or a Rails credential lookup. TablePro leaves those out rather than guessing, so a row you expected may be missing. Fill those connections in by hand, or paste the URL with Import from URL.