Unable to connect to site with Sequel Pro with Mac Lighting

I am trying to test out Local without removing Valet. I have stopped valet, and Local starts fine, but would not run Sequel Pro correctly. I created a new WordPress site test. I suspect it is a PATH issue. Here is what I have:

/usr/local/sbin
/Users/riskiii/Library/Python/3.7/bin
/Users/riskiii/.zplug/bin
/Users/riskiii/.zshlocal
/Users/riskiii/.dotfiles/bin
/Applications/Local.app/Contents/Resources/extraResources/site-binaries/mysql-8.0.15/bin/
/Applications/Local.app/Contents/Resources/extraResources/shell-scripts/
/Users/riskiii/.composer/vendor/bin
/Users/riskiii/bin/valet
/Users/riskiii/bin
…

I then tried opening Local with open /Applications/Local.app and then starting Sequel Pro the normal way. I do have Sequel Pro already installed. I suspect I would need the path for Nginx and whatever is left, but WordPress runs fine.

IT IS SUPER FAST!!!

local-lightning.log (26.7 KB)

MySQL 8.0 needs the Sequel Pro nightly.

https://sequelpro.com/test-builds

1 Like

Cool, that has Sequel Pro Running. What do I need to put in my Path to start all of it correctly?

As long as you swap out the stable version of Sequel Pro with the nightly build, you should be good to go!

Are there plans to use an alternative like Sequel Pro Ace since Sequel Pro is not being developed/supported anymore? It’s been crashing more regularly for me.

1 Like

I was just wondering the same thing… It’s like I follow you on Twitter or something.

After I deleted Sequel Pro Nightly, it seems like Local recognizes Sequel Ace and tries to use it… but fails.

Note: The process to get there was:
Open Local (with Sequel Pro still installeD)
Delete Sequel Pro
Try to use “Open in Sequel Pro” button.

After that failed I closed Local, reopened Local and Local switched the link back to “Download Sequel Pro”.

2020-06-30 at 3.38 PM

Fancy seeing you here! :slight_smile:

Also worth noting that others have been using TablePress now, and using the sockets approach it can work with Local: https://twitter.com/royboy789/status/1277730487063150595?s=20

It requires manual setup work, but can be integrated.

Hey @jb510 and @scottbuscemi! Long time no see!

I actually just finished posting a github issue to Sequel Ace about this (https://github.com/Sequel-Ace/Sequel-Ace/issues/113#issuecomment-652116190) because I was also having this issue.

I also have an issue open for opening the DB in Sequel Ace via a URL scheme (https://github.com/Sequel-Ace/Sequel-Ace/issues/108) which is how I assume the “Open in Sequel Pro” functionality in Local is supposed to work so that we can build a Local add-on that opens the DB in Sequel Ace. I’ll post an update here if I hear back from them and they get this working.

As a side note, let me know if there are other conveniences that you’d like to see in Local. We just released an add-on for Local and are looking to develop more.

1 Like

Ah… interesting. I figured it might be a file permission issue based on the error message in the screenshot above, but was thinking about it in reverse.

On a whim I tried setting macOS security for Ace to “Full disk access” doesn’t fix it either, but I suspect that’s the route they’re going to need to take to grant Ace access to sockets outside the app.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.